CVE-2024-27003: clk: Get runtime PM before walking tree for clk_summary
In the Linux kernel, the following vulnerability has been resolved:
clk: Get runtime PM before walking tree for clksummary
Similar to the previous commit, we should make sure that all devices are runtime resumed before printing the clksummary through debugfs. Failure to do so would result in a deadlock if the thread is resuming a device to print clk state and that device is also runtime resuming in another thread, e.g the screen is turning on and the display driver is starting up. We remove the calls to clkpmruntime{get,put}() in this path because they're superfluous now that we know the devices are runtime resumed. This also squashes a bug where the return value of clkpmruntimeget() wasn't checked, leading to an RPM count underflow on error paths.
Other sources
In the Linux kernel, the following vulnerability has been resolved:
clk: Get runtime PM before walking tree for clksummary
The Linux kernel CVE team has assigned CVE-2024-27003 to this issue.
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024050146-CVE-2024-27003-c862@gregkh/T
— Red Hat
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-27003?
CVE-2024-27003 has been classified as a moderate severity vulnerability in the Linux kernel.
How do I fix CVE-2024-27003?
To fix CVE-2024-27003, ensure your Linux kernel is updated to version 6.1.88, 6.6.29, 6.8.8, or 6.9.
What systems are affected by CVE-2024-27003?
CVE-2024-27003 affects various versions of the Linux kernel prior to updates that include the fix.
Is CVE-2024-27003 exploitable remotely?
CVE-2024-27003 does not appear to be remotely exploitable based on the current information available.
What is the impact of CVE-2024-27003 on systems?
The impact of CVE-2024-27003 may include potential security risks related to device runtime performance in the Linux kernel.