CVE-2024-27004: Linux kernel · clk: Get runtime PM before walking tree during disable_unused
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.4.0-1128.138~18.04.1 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 15:21 UTC
- Patch
- Available – fixed in 5.4.0-1128.138~18.04.1, 5.4.0-1133.140~18.04.1, 5.4.0-1132.141~18.04.1 +68
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6893-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6893-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-6893-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-4 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-ibmpkg:deb/ubuntu/linux-ibm?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available and has been released in multiple Linux kernel versions including 5.4.0-1075.80~18.04.1 and later. Users and administrators should apply these official patches to resolve the deadlock issue. No additional mitigation steps are required beyond applying the vendor-provided updates.
Description
CVE-2024-27004 is a deadlock vulnerability in the Linux kernel's clock (clk) subsystem. It occurs when runtime power management (PM) resume operations are performed while holding the clk prepare_lock, causing two threads to wait indefinitely on each other. This deadlock can lead to hung tasks and system instability. The issue has been fixed in multiple Linux kernel versions starting from 5.4.0-1075.80~18.04.1 and related releases.
References
- ubuntu.com/security/CVE-2024-27004 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-27004 (opens in a new tab)
- git.kernel.org/linus/e581cf5d216289ef292d1a4036d53ce90e122469 (opens in a new tab)
- git.kernel.org/stable/c/a29ec0465dce0b871003698698ac6fa92c9a5034 (opens in a new tab)
- git.kernel.org/stable/c/a424e713e0cc33d4b969cfda25b9f46df4d7b5bc (opens in a new tab)
- git.kernel.org/stable/c/60ff482c4205a5aac3b0595ab794cfd62295dab5 (opens in a new tab)
- git.kernel.org/stable/c/115554862294397590088ba02f11f2aba6d5016c (opens in a new tab)
- git.kernel.org/stable/c/e581cf5d216289ef292d1a4036d53ce90e122469 (opens in a new tab)
- ubuntu.com/security/notices/USN-6893-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6893-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-6893-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-4 (opens in a new tab)