CVE-2024-27003

clk: Get runtime PM before walking tree for clk_summary

MEDIUM
5.5
CVSS Score
Published: May 1, 2024 at 05:28 AM UTC
Updated: June 17, 2026 at 07:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: clk: Get runtime PM before walking tree for clk_summary Similar to the previous commit, we should make sure that all devices are runtime resumed before printing the clk_summary 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 clk_pm_runtime_{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 clk_pm_runtime_get() wasn't checked, leading to an RPM count underflow on error paths.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.17 ≤ v < 6.1.885.17 ≤ v < 6.6.295.17 ≤ v < 6.8.85.17 ≤ v < 6.96.2 ≤ v < 6.6.296.7 ≤ v < 6.8.81bb294a7981c737e2311a78e4086635ac0220ace6.9 rc16.9 rc26.9 rc36.9 rc4
Vendor states this is fixed in 2c077fdfd09dffb31a890e5095c8ab205138a42e (fixed)
Vendor states this is fixed in 83ada89e4a86e2b28ea2b5113c76d6dc7560a4d0 (fixed)
Vendor states this is fixed in 9d1e795f754db1ac3344528b7af0b17b8146f321 (fixed)
Vendor states this is fixed in b457105309d388e4081c716cf7b81d517ff74db4 (fixed)
Vendor states this is fixed in 5.17 (unaffected)
Vendor states this is fixed in 6.1.88 (unaffected)
Vendor states this is fixed in 6.6.29 (unaffected)
Vendor states this is fixed in 6.8.8 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card