CVE-2026-64502
Received Received - Intake

Heap Corruption in Linux Kernel IIO ADC Sigma Delta Driver

Vulnerability report for CVE-2026-64502, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-25

Last updated on: 2026-07-25

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: iio: adc: ad_sigma_delta: fix clear_pending_event for registerless devices ad_sigma_delta_clear_pending_event() falls through to the status register read path for devices with has_registers = false and no rdy_gpiod. For such devices, ad_sd_read_reg() skips the address byte entirely and clocks raw MISO bytes with no address phase β€” making it byte-for-byte identical to reading conversion data. If a pending conversion result is present, this partially consumes it and corrupts the data stream for the subsequent ad_sd_read_reg() call in ad_sigma_delta_single_conversion(). Furthermore, with num_resetclks = 0 on these devices, data_read_len evaluates to 0. If the clocked byte has bit 7 clear, pending_event is set and the code attempts memset(data + 2, 0xff, 0 - 1), overflowing to SIZE_MAX and corrupting the heap. Fix by returning 0 immediately when neither rdy_gpiod nor has_registers is set. This is safe for all current registerless devices: ad7191 and ad7780 (with powerdown GPIO) are reset between conversions by CS deassertion, so there is no stale result to drain; ad7780 (without powerdown GPIO) and max11205 are continuously-converting and cycle ~DRDY at the output data rate regardless of whether the previous result was read, so the next falling edge fires naturally. A future registerless device that holds ~DRDY asserted until data is read would be broken by this early return and would require either num_resetclks set or a rdy-gpio. The same heap corruption is reachable on any device with rdy_gpiod set but num_resetclks = 0: if the GPIO indicates a pending event, the drain path executes memset(data + 2, 0xff, 0 - 1) regardless of has_registers. Add an explicit data_read_len == 0 guard after the pending event check; the stale result is then consumed by the first ad_sd_read_reg() call in ad_sigma_delta_single_conversion().

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-25
Last Modified
2026-07-25
Generated
2026-07-25
AI Q&A
2026-07-25
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux_kernel linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the Linux kernel's IIO ADC subsystem, specifically devices using the ad_sigma_delta driver. It occurs in registerless devices where a function incorrectly processes pending conversion events, leading to data corruption or heap overflow. The issue arises when the driver attempts to read a status register that doesn't exist, causing it to misinterpret conversion data as status information.

Detection Guidance

This vulnerability is specific to the Linux kernel's IIO ADC subsystem and affects registerless devices like ad7191, ad7780, and max11205. Detection requires checking the kernel version and verifying if the affected ADC drivers are in use. No direct network detection commands are applicable. Inspect kernel logs for errors related to ad_sigma_delta or ADC drivers.

Impact Analysis

If you use affected devices like ad7191, ad7780, or max11205 with the Linux kernel, this flaw could cause system instability, data corruption, or crashes. It may lead to incorrect sensor readings or unexpected behavior in applications relying on these ADC devices.

Mitigation Strategies

Apply the latest kernel update from your distribution to patch the vulnerability. If using custom kernels, ensure the fix for CVE-2026-64502 is included. Monitor system logs for ADC-related errors post-update. For devices using ad7191, ad7780, or max11205, verify proper configuration to avoid heap corruption.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-64502. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart