LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27038: clk: Fix clk_core_get NULL dereference

In the Linux kernel, the following vulnerability has been resolved: clk: Fix clk_core_get NULL dereference It is possible for clk_core_get to dereference a NULL in the following sequence: clk_core_get() of_clk_get_hw_from_clkspec() __of_clk_get_hw_from_provider() __clk_get_hw() __clk_get_hw() can return NULL which is dereferenced by clk_core_get() at hw->core. Prior to commit dde4eff47c82 ("clk: Look for parents with clkdev based clk_lookups") the check IS_ERR_OR_NULL() was performed which would have caught the NULL. Reading the description of this function it talks about returning NULL but that cannot be so at the moment. Update the function to check for hw before dereferencing it and return NULL if hw is NULL.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-27038 is a Linux kernel bug where clock-management code can dereference a missing object. In practical terms, affected systems may be exposed to kernel instability or denial of service if the vulnerable path is reachable. The sources do not provide CVSS, attack prerequisites, or evidence of active exploitation.

Executive priority

Address through normal kernel patch management, with higher priority for embedded, industrial, or high-availability systems. There is no cited active exploitation, but kernel crash risk can still create operational disruption.

Technical view

The flaw is in clk_core_get(). __clk_get_hw() can return NULL through the clock provider lookup path, and clk_core_get() dereferenced hw->core without checking. Stable kernel commits add the missing NULL check and return NULL when no clock hardware object is available.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or vendor products that include them. The bundle lists Linux as affected and includes Debian LTS and Siemens references, but does not identify all downstream products or reachable configurations.

Exploitation context

No active exploitation is cited, and KEV status is false. The provided record does not describe remote attackability, privileges required, or a public exploit. Treat this primarily as a kernel availability and stability risk until vendor advisories provide more detail.

Researcher notes

The record ties the regression to commit dde4eff47c82 and restores prior IS_ERR_OR_NULL-style behavior by checking hw before dereference. Evidence is patch-level; exploitability, configuration dependency, and impact severity are not fully specified in the supplied sources.

Mitigation direction

  • Update to a vendor-supported kernel containing the stable clk fix.
  • Apply Debian, Siemens, or other platform-specific security updates where applicable.
  • For appliances, request firmware guidance from the device vendor.
  • Prioritize systems where kernel crashes would affect safety or uptime.
  • Track vendor advisories because source impact details are incomplete.

Validation and detection

  • Inventory running kernel versions across servers, appliances, and embedded devices.
  • Compare kernel builds against vendor advisories and listed stable fix commits.
  • Confirm distribution packages include the clk NULL-check patch.
  • Review affected Siemens or other device advisories for product-specific exposure.
  • Monitor logs for kernel oops or panic events involving clock framework paths.
Prepared
Confidence
medium
Sources
12

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-27038 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
3ADP providers
11Source 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
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxdde4eff47c82c52a72af333d9e55370eee6d95d6, dde4eff47c82c52a72af333d9e55370eee6d95d6, dde4eff47c82c52a72af333d9e55370eee6d95d6, dde4eff47c82c52a72af333d9e55370eee6d95d6, dde4eff47c82c52a72af333d9e55370eee6d95d6, dde4eff47c82c52a72af333d9e55370eee6d95d6, dde4eff47c82c52a72af333d9e55370eee6d95d6, dde4eff47c82c52a72af333d9e55370eee6d95d6unaffected
LinuxLinux5.2, 0, 5.4.273, 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 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.