LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38133: iio: adc: ad4851: fix ad4858 chan pointer handling

In the Linux kernel, the following vulnerability has been resolved: iio: adc: ad4851: fix ad4858 chan pointer handling The pointer returned from ad4851_parse_channels_common() is incremented internally as each channel is populated. In ad4858_parse_channels(), the same pointer was further incremented while setting ext_scan_type fields for each channel. This resulted in indio_dev->channels being set to a pointer past the end of the allocated array, potentially causing memory corruption or undefined behavior. Fix this by iterating over the channels using an explicit index instead of incrementing the pointer. This preserves the original base pointer and ensures all channel metadata is set correctly.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux driver for the AD4858 analog-to-digital converter can retain an invalid channel-array pointer during device setup. This may corrupt kernel memory, potentially causing crashes or allowing a locally authenticated user to affect confidentiality, integrity, and availability. Exposure depends on running an affected kernel with the relevant hardware and driver path.

Executive priority

Prioritize targeted remediation rather than an organization-wide emergency. Quickly identify affected kernels using this specialized ADC driver, then update exposed systems through supported distribution channels. Treat affected multi-user, appliance, laboratory, and industrial systems more urgently because the stated impact includes complete confidentiality, integrity, and availability compromise.

Technical view

The AD4851 IIO driver’s AD4858 channel parser advanced an already incremented pointer, causing indio_dev->channels to reference memory beyond the allocated array. Later access could produce memory corruption or undefined behavior. The correction uses indexed iteration, preserving the allocation’s base pointer while setting channel metadata.

Likely exposure

Likely limited to systems using an affected Linux kernel where the AD4858-related driver is present and exercised. The supplied CVSS vector requires local access and low privileges. The bundle identifies the 6.15 line through 6.15.3 and a 6.16 boundary, but exact distribution package exposure requires vendor confirmation.

Exploitation context

The supplied record is not in CISA KEV and provides no evidence of active exploitation or a public exploit. CVSS 3.1 rates it 7.8 because successful local exploitation could potentially compromise confidentiality, integrity, and availability. Practical reachability likely depends on the driver and compatible device configuration.

Researcher notes

The root cause is base-pointer loss during channel metadata construction, not a generic userspace parsing issue. The sources establish potential memory corruption but do not describe a demonstrated exploitation primitive, affected distributions, or exact fixed package versions. Validate reachability through kernel configuration, module state, hardware presence, and vendor backport status.

Mitigation direction

  • Follow Linux kernel or distribution guidance for CVE-2025-38133.
  • Update to a vendor-supported kernel containing the referenced channel-pointer correction.
  • Prioritize systems using AD4858 hardware or loading the affected IIO driver.
  • If updates are delayed, restrict local access and unnecessary driver exposure.

Validation and detection

  • Inventory kernel versions and compare them with distribution advisories for CVE-2025-38133.
  • Determine whether the AD4851/AD4858 IIO driver is installed, enabled, or loaded.
  • Identify systems connected to compatible AD4858 converter hardware.
  • Confirm the installed kernel includes one of the referenced upstream corrections.
  • After updating, verify normal device initialization and review logs for driver or memory errors.
Prepared
Confidence
high
Sources
4

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-2025-38133 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38133Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6250803fe2ec92be32a4df1c3a39c4a460d5bd58, 6250803fe2ec92be32a4df1c3a39c4a460d5bd58unaffected
LinuxLinux6.15, 0, 6.15.3, 6.16affected
Weakness

CWE details

No CWE listed

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