LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42100: clk: sunxi-ng: common: Don't call hw_to_ccu_common on hw without common

In the Linux kernel, the following vulnerability has been resolved: clk: sunxi-ng: common: Don't call hw_to_ccu_common on hw without common In order to set the rate range of a hw sunxi_ccu_probe calls hw_to_ccu_common() assuming all entries in desc->ccu_clks are contained in a ccu_common struct. This assumption is incorrect and, in consequence, causes invalid pointer de-references. Remove the faulty call. Instead, add one more loop that iterates over the ccu_clks and sets the rate range, if required.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-42100 is a Linux kernel defect in the sunxi-ng clock driver. During probing, the kernel could dereference an invalid pointer because it assumed every clock entry had a common structure. Business urgency depends on whether affected Linux kernels and this driver are present.

Executive priority

Treat as a targeted kernel maintenance issue unless your environment uses affected sunxi-ng platforms. Without CVSS, KEV, or exploitation evidence, prioritize normal patch management, with faster handling for exposed embedded or appliance fleets.

Technical view

The flaw is in clk/sunxi-ng common code. sunxi_ccu_probe called hw_to_ccu_common() on ccu_clks entries that may not be embedded in ccu_common, causing invalid pointer dereferences. The resolved change removes the faulty call and sets rate ranges through a safer iteration.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the sunxi-ng clock driver path in use. The source bundle lists Linux kernel versions and stable commits but does not map exposure to distributions, appliances, or cloud images.

Exploitation context

No KEV listing is present, and the supplied sources do not claim active exploitation or public exploit availability. The described impact is an invalid pointer dereference in kernel driver initialization logic, but exploitability and attacker prerequisites are not established in the bundle.

Researcher notes

The evidence supports a kernel pointer dereference bug in clk/sunxi-ng probe handling. The bundle does not provide CVSS, CWE, crash traces, distribution impact, or exploit prerequisites, so exposure analysis should be branch- and vendor-specific.

Mitigation direction

  • Inventory Linux kernel versions across affected systems.
  • Check whether kernels include the referenced stable fixes.
  • Apply vendor-provided kernel updates containing the resolved change.
  • Prioritize systems using the sunxi-ng clock driver path.
  • Track distribution advisories for package-specific fixed versions.

Validation and detection

  • Compare deployed kernels against vendor advisories and fixed stable commits.
  • Review kernel configuration and hardware usage for sunxi-ng clock support.
  • Confirm patched source removes the faulty hw_to_ccu_common call path.
  • Run standard post-update boot and hardware regression checks.
Prepared
Confidence
medium
Sources
5

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-42100 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
4Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux547263745e15a038ec3954b5c283805529377626, b914ec33b391ec766545a41f0cfc0de3e0b388d7, b914ec33b391ec766545a41f0cfc0de3e0b388d7, 761cbd9c0e4ed082b548bf6a0de25eebad24309d, 6.6.31, 6.8.10unaffected
LinuxLinux6.9, 0, 6.6.39, 6.9.9, 6.10affected
Weakness

CWE details

No CWE listed

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