CVE-2024-57799: phy: rockchip: samsung-hdptx: Set drvdata before enabling runtime PM
In the Linux kernel, the following vulnerability has been resolved:
phy: rockchip: samsung-hdptx: Set drvdata before enabling runtime PM
In some cases, rkhdptxphyruntimeresume() may be invoked before platformsetdrvdata() is executed in ->probe(), leading to a NULL pointer dereference when using the return of devgetdrvdata().
Ensure platformsetdrvdata() is called before devmpmruntimeenable().
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.27-1 - Configuration
Call platform_set_drvdata() before devm_pm_runtime_enable() in the probe path so rk_hdptx_phy_runtime_resume() cannot use a NULL dev_get_drvdata() result.
Linux kernel phy: rockchip: samsung-hdptx platform_set_drvdata() ordering = before devm_pm_runtime_enable()
Event History
Frequently Asked Questions
What is the severity of CVE-2024-57799?
CVE-2024-57799 has a medium severity due to potential NULL pointer dereference which can lead to system instability.
How do I fix CVE-2024-57799?
To fix CVE-2024-57799, update the Linux kernel to a version later than 6.12.8 or apply the relevant patches.
Which versions of Linux Kernel are affected by CVE-2024-57799?
CVE-2024-57799 affects Linux Kernel versions from 6.9 to 6.12.8, including specific release candidates 6.13-rc1 to 6.13-rc4.
What causes the vulnerability CVE-2024-57799?
CVE-2024-57799 is caused by the invocation of rk_hdptx_phy_runtime_resume() before platform_set_drvdata() in the driver probe sequence.
Is CVE-2024-57799 being actively exploited?
As of now, there are no reports indicating that CVE-2024-57799 is actively exploited in the wild.