NVD / CVE Program· CNA Linux

CVE-2024-27004: clk: Get runtime PM before walking tree during disable_unused

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 115554862294397590088ba02f11f2aba6d5016c, 253ab38d1ee652a596942156978a233970d185ba, 4af115f1a20a3d9093586079206ee37c2ac55123; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 115554862294397590088ba02f11f2aba6d5016c, 253ab38d1ee652a596942156978a233970d185ba, 4af115f1a20a3d9093586079206ee37c2ac55123; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: clk: Get runtime PM before walking tree during disable_unused Doug reported [1] the following hung task: INFO: task swapper/0:1 blocked for more than 122 seconds. Not tainted 5.15.149-21875-gf795ebc40eb8 #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:swapper/0 state:D stack: 0 pid: 1 ppid: 0 flags:0x00000008 Call trace: __switch_to+0xf4/0x1f4 __schedule+0x418/0xb80 schedule+0x5c/0x10c rpm_resume+0xe0/0x52c rpm_resume+0x178/0x52c __pm_runtime_resume+0x58/0x98 clk_pm_runtime_get+0x30/0xb0 clk_disable_unused_subtree+0x58/0x208 clk_disable_unused_subtree+0x38/0x208 clk_disable_unused_subtree+0x38/0x208 clk_disable_unused_subtree+0x38/0x208 clk_disable_unused_subtree+0x38/0x208 clk_disable_unused+0x4c/0xe4 do_one_initcall+0xcc/0x2d8 do_initcall_level+0xa4/0x148 do_initcalls+0x5c/0x9c do_basic_setup+0x24/0x30 kernel_init_freeable+0xec/0x164 kernel_init+0x28/0x120 ret_from_fork+0x10/0x20 INFO: task kworker/u16:0:9 blocked for more than 122 seconds. Not tainted 5.15.149-21875-gf795ebc40eb8 #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/u16:0 state:D stack: 0 pid: 9 ppid: 2 flags:0x00000008 Workqueue: events_unbound deferred_probe_work_func Call trace: __switch_to+0xf4/0x1f4 __schedule+0x418/0xb80 schedule+0x5c/0x10c schedule_preempt_disabled+0x2c/0x48 __mutex_lock+0x238/0x488 __mutex_lock_slowpath+0x1c/0x28 mutex_lock+0x50/0x74 clk_prepare_lock+0x7c/0x9c clk_core_prepare_lock+0x20/0x44 clk_prepare+0x24/0x30 clk_bulk_prepare+0x40/0xb0 mdss_runtime_resume+0x54/0x1c8 pm_generic_runtime_resume+0x30/0x44 __genpd_runtime_resume+0x68/0x7c genpd_runtime_resume+0x108/0x1f4 __rpm_callback+0x84/0x144 rpm_callback+0x30/0x88 rpm_resume+0x1f4/0x52c rpm_resume+0x178/0x52c __pm_runtime_resume+0x58/0x98 __device_attach+0xe0/0x170 device_initial_probe+0x1c/0x28 bus_probe_device+0x3c/0x9c device_add+0x644/0x814 mipi_dsi_device_register_full+0xe4/0x170 devm_mipi_dsi_device_register_full+0x28/0x70 ti_sn_bridge_probe+0x1dc/0x2c0 auxiliary_bus_probe+0x4c/0x94 really_probe+0xcc/0x2c8 __driver_probe_device+0xa8/0x130 driver_probe_device+0x48/0x110 __device_attach_driver+0xa4/0xcc bus_for_each_drv+0x8c/0xd8 __device_attach+0xf8/0x170 device_initial_probe+0x1c/0x28 bus_probe_device+0x3c/0x9c deferred_probe_work_func+0x9c/0xd8 process_one_work+0x148/0x518 worker_thread+0x138/0x350 kthread+0x138/0x1e0 ret_from_fork+0x10/0x20 The first thread is walking the clk tree and calling clk_pm_runtime_get() to power on devices required to read the clk hardware via struct clk_ops::is_enabled(). This thread holds the clk prepare_lock, and is trying to runtime PM resume a device, when it finds that the device is in the process of resuming so the thread schedule()s away waiting for the device to finish resuming before continuing. The second thread is runtime PM resuming the same device, but the runtime resume callback is calling clk_prepare(), trying to grab the prepare_lock waiting on the first thread. This is a classic ABBA deadlock. To properly fix the deadlock, we must never runtime PM resume or suspend a device with the clk prepare_lock held. Actually doing that is near impossible today because the global prepare_lock would have to be dropped in the middle of the tree, the device runtime PM resumed/suspended, and then the prepare_lock grabbed again to ensure consistency of the clk tree topology. If anything changes with the clk tree in the meantime, we've lost and will need to start the operation all over again. Luckily, most of the time we're simply incrementing or decrementing the runtime PM count on an active device, so we don't have the chance to schedule away with the prepare_lock held. Let's fix this immediate problem that can be ---truncated---

MediumCVSS 5.5 · v3.1—No exploit Fix available

Denial of service

BDU:2024-09330

Published: May 1, 2024
Updated: Oct 15, 2026
EPSS: 0.2% · 11th percentile
CWE: CWE-667

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel
debian	debian linux	cpe:2.3:o:debian:debian_linux
fedoraproject	fedora	cpe:2.3:o:fedoraproject:fedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

debian debian linux10.0
fedoraproject fedora38
fedoraproject fedora39
fedoraproject fedora40
linux linux kernel6.2 and later · before 6.6.29
linux linux kernel4.15 and later · before 5.4.275
linux linux kernel6.7 and later · before 6.8.8
linux linux kernel5.5 and later · before 5.10.216
linux linux kernel5.11 and later · before 5.15.157
linux linux kernel5.16 and later · before 6.1.88
linux linux kernel6.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 4.15affected
- 9a34b45397e5a389e25a0c5d39983300d040e5e2 and later · before 253ab38d1ee652a596942156978a233970d185baaffected · git
- 9a34b45397e5a389e25a0c5d39983300d040e5e2 and later · before 4af115f1a20a3d9093586079206ee37c2ac55123affected · git
- 9a34b45397e5a389e25a0c5d39983300d040e5e2 and later · before a29ec0465dce0b871003698698ac6fa92c9a5034affected · git
- 9a34b45397e5a389e25a0c5d39983300d040e5e2 and later · before a424e713e0cc33d4b969cfda25b9f46df4d7b5bcaffected · git
- 9a34b45397e5a389e25a0c5d39983300d040e5e2 and later · before 60ff482c4205a5aac3b0595ab794cfd62295dab5affected · git
- 9a34b45397e5a389e25a0c5d39983300d040e5e2 and later · before 115554862294397590088ba02f11f2aba6d5016caffected · git
- 9a34b45397e5a389e25a0c5d39983300d040e5e2 and later · before e581cf5d216289ef292d1a4036d53ce90e122469affected · git
- before 4.15not affected · semver
- 5.4.275 and later · up to and including 5.4.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.90-1	6.1.90-1
Debian:13	linux	before 6.8.9-1	6.8.9-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2024-26988May 1, 2024 · init/main.c: Fix potential static_command_line memory overflow
31Monitor
← EarlierCVE-2024-26993May 1, 2024 · fs: sysfs: Fix reference leak in sysfs_break_active_protection()
22Monitor
Later →CVE-2024-27005May 1, 2024 · interconnect: Don't access req_list while it's being manipulated
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	115554862294397590088ba02f11f2aba6d5016c	Vendor (CNA)
Linux Linux	253ab38d1ee652a596942156978a233970d185ba	Vendor (CNA)
Linux Linux	4af115f1a20a3d9093586079206ee37c2ac55123	Vendor (CNA)
Linux Linux	60ff482c4205a5aac3b0595ab794cfd62295dab5	Vendor (CNA)
Linux Linux	a29ec0465dce0b871003698698ac6fa92c9a5034	Vendor (CNA)
Linux Linux	a424e713e0cc33d4b969cfda25b9f46df4d7b5bc	Vendor (CNA)
Linux Linux	e581cf5d216289ef292d1a4036d53ce90e122469	Vendor (CNA)
azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0	6.6.35.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0	6.6.35.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
debian:linux	6.1.90-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).