LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26711: iio: adc: ad4130: zero-initialize clock init data

In the Linux kernel, the following vulnerability has been resolved: iio: adc: ad4130: zero-initialize clock init data The clk_init_data struct does not have all its members initialized, causing issues when trying to expose the internal clock on the CLK pin. Fix this by zero-initializing the clk_init_data struct.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in the AD4130 ADC driver. An internal clock setup structure was not fully initialized, which could cause problems when exposing the internal clock on the CLK pin. The sources do not provide CVSS, impact detail, or evidence of active exploitation.

Executive priority

Handle through normal kernel patch governance, with higher priority for embedded, industrial, or appliance systems using this ADC driver. Current public evidence does not support emergency response.

Technical view

CVE-2024-26711 is resolved by zero-initializing clk_init_data in the Linux kernel iio adc ad4130 driver. The reported fault is incomplete struct initialization during internal clock exposure on the CLK pin. Public sources identify affected Linux kernel versions but do not describe exploit primitives, privilege requirements, or security impact.

Likely exposure

Exposure appears limited to Linux systems running affected kernels where the AD4130 ADC driver is present and relevant hardware or CLK pin functionality is used. General-purpose servers are unlikely to be exposed unless this driver path is enabled and used.

Exploitation context

The bundle does not cite active exploitation, CISA KEV inclusion, public exploit availability, or a demonstrated attack path. Treat this as a kernel maintenance issue unless vendor advisories add stronger impact evidence.

Researcher notes

The record lacks CVSS, CWE, exploitability analysis, and detailed impact. Analysis should focus on the ad4130 driver change, affected kernel branches, and whether the vulnerable clock initialization path is reachable in deployed configurations.

Mitigation direction

  • Update to a Linux kernel containing the stable fix or equivalent vendor backport.
  • Check distribution and device vendor advisories for supported patched kernel packages.
  • Prioritize embedded or hardware-integrated systems using the AD4130 ADC driver.
  • Track the referenced upstream stable commits for backport confirmation.

Validation and detection

  • Inventory Linux kernel versions across potentially affected assets.
  • Check whether the AD4130 ADC driver is built, loaded, or used.
  • Confirm patched kernels include one referenced stable commit or a vendor equivalent.
  • Review device configurations where AD4130 internal clock exposure is relevant.
Prepared
Confidence
medium
Sources
5

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-26711 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux62094060cf3acaf52e277457d807ea753269b89e, 62094060cf3acaf52e277457d807ea753269b89e, 62094060cf3acaf52e277457d807ea753269b89eunaffected
LinuxLinux6.2, 0, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

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