CVE-2026-64502
High 7.8No known exploitationFix availableiio: adc: ad_sigma_delta: fix clear_pending_event for registerless devices
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 7% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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().
Weakness: CWE-190
Patching and mitigation
- Patch status
- Fix available (source: NVD (reference tagged Patch))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- git.kernel.org (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 132d44dc6966c1cf841ffe0f6f048165687e870b before 91bc6767a4f55dc470d8a56b55b9f2ea09094efe | 91bc6767a4f55dc470d8a56b55b9f2ea09094efe | CVE Program |
| Linux | Linux | from 132d44dc6966c1cf841ffe0f6f048165687e870b before 3394e0b3328422431cadaf314fa58d3717ed4936 | 3394e0b3328422431cadaf314fa58d3717ed4936 | CVE Program |
| Linux | Linux | from 132d44dc6966c1cf841ffe0f6f048165687e870b before 3bceb26dfaf7ba805b459e41c1d0ba916862dade | 3bceb26dfaf7ba805b459e41c1d0ba916862dade | CVE Program |
| Linux | Linux | 6.14 | Not documented | CVE Program |
| linux | linux_kernel | from 6.14 before 6.18.39 | 6.18.39 | NIST NVD |
| linux | linux_kernel | from 6.19 before 7.1.4 | 7.1.4 | NIST NVD |
| Linux | Linux (unaffected) | from 6.18.39 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.1.4 up to and including 7.1.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.2 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.14 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by NVD (reference tagged Patch)