LiveActive security incident?Get immediate response
CVE Record

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 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can deadlock a system path that prints clock information through debugfs while devices are resuming from power management. The likely business impact is availability disruption, not confirmed data theft or remote compromise. The sources do not provide a CVSS score or report active exploitation.

Executive priority

Treat this as a normal-priority Linux kernel availability fix unless affected systems are operationally sensitive, kiosk-like, embedded, or difficult to reboot. Prioritize through standard kernel maintenance rather than emergency response, because active exploitation and severe impact are not supported by the provided sources.

Technical view

The clock subsystem's clk_summary debugfs path did not runtime-resume all devices before walking the clock tree. Concurrent runtime resume activity could deadlock, and an unchecked clk_pm_runtime_get() return could underflow runtime PM accounting on error paths. Stable kernel commits address the logic.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel builds with debugfs clock summary access available. The source bundle lists Linux kernel versions around 5.17 and stable fixes including 6.1.88, 6.6.29, 6.8.8, and 6.9; confirm exact distro package status.

Exploitation context

CISA KEV is false in the provided bundle, and no cited source reports exploitation in the wild. The described condition involves debugfs clk_summary access racing with runtime power-management resume activity, such as display startup. Evidence supports denial-of-service style risk, not privilege escalation or remote code execution.

Researcher notes

The useful review points are the clk_summary debugfs path, runtime PM ordering, and the removal of redundant clk_pm_runtime_get/put calls after ensuring devices are resumed. The source evidence is limited to the CVE text, kernel stable commits, and Fedora package announcements.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Use distribution advisories, including Fedora notices where applicable, to identify fixed packages.
  • If patching is delayed, review vendor guidance for debugfs access restrictions.
  • Schedule reboot or live-patching steps required for the fixed kernel to take effect.

Validation and detection

  • Inventory Linux kernel versions across servers, workstations, appliances, and embedded systems.
  • Map installed kernels to vendor advisories or the referenced stable commits.
  • Check whether debugfs is mounted and who can access clock summary data.
  • Confirm the running kernel after remediation, not only the installed package version.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-27003 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1bb294a7981c737e2311a78e4086635ac0220ace, 1bb294a7981c737e2311a78e4086635ac0220ace, 1bb294a7981c737e2311a78e4086635ac0220ace, 1bb294a7981c737e2311a78e4086635ac0220aceunaffected
LinuxLinux5.17, 0, 6.1.88, 6.6.29, 6.8.8, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.