[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025011151-CVE-2024-57799-ae66@gregkh>
Date: Sat, 11 Jan 2025 13:39:54 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-57799: phy: rockchip: samsung-hdptx: Set drvdata before enabling runtime PM
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
phy: rockchip: samsung-hdptx: Set drvdata before enabling runtime PM
In some cases, rk_hdptx_phy_runtime_resume() may be invoked before
platform_set_drvdata() is executed in ->probe(), leading to a NULL
pointer dereference when using the return of dev_get_drvdata().
Ensure platform_set_drvdata() is called before devm_pm_runtime_enable().
The Linux kernel CVE team has assigned CVE-2024-57799 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.9 with commit 553be2830c5f33308483e8118de748a2c69fe593 and fixed in 6.12.8 with commit 7061849a4a1752a06944a819dd1f7bfd58df7383
Issue introduced in 6.9 with commit 553be2830c5f33308483e8118de748a2c69fe593 and fixed in 6.13-rc5 with commit 9d23e48654620fdccfcc74cc2cef04eaf7353d07
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-57799
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/7061849a4a1752a06944a819dd1f7bfd58df7383
https://git.kernel.org/stable/c/9d23e48654620fdccfcc74cc2cef04eaf7353d07
Powered by blists - more mailing lists