PatchSiren cyber security CVE debrief
CVE-2026-64502 Linux CVE debrief
A vulnerability in the Linux kernel's iio: adc: ad_sigma_delta driver can lead to heap corruption. The ad_sigma_delta_clear_pending_event function does not properly handle devices without registers, causing it to consume and corrupt conversion data. Additionally, on devices with rdy_gpiod set but num_resetclks = 0, a pending event check can lead to memset overflowing to SIZE_MAX and corrupting the heap. The fix involves returning 0 immediately when neither rdy_gpiod nor has_registers is set, and adding an explicit data_read_len == 0 guard after the pending event check.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 7.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-25
- Original CVE updated
- 2026-11-03
- Advisory published
- 2026-07-25
- Advisory updated
- 2026-11-03
Who should care
Defenders responsible for Linux kernel-based systems, particularly those using the ad_sigma_delta driver, should assess exposure and prioritize patching. This includes administrators and security teams managing Linux kernel deployments.
Why it matters
A vulnerability in the Linux kernel's iio: adc: ad_sigma_delta driver can lead to heap corruption and data corruption. Defenders should prioritize verifying and applying patches, reviewing device configurations, and assessing exposure.
- Potential heap corruption on devices without registers
- Potential data corruption on devices with rdy_gpiod set but num_resetclks = 0
- Need for verification of Linux kernel versions and device configurations
- Priority for patching and updating Linux kernel deployments
Technical summary
The ad_sigma_delta_clear_pending_event function in the Linux kernel's iio: adc: ad_sigma_delta driver does not properly handle devices without registers. This can cause it to consume and corrupt conversion data. On devices with rdy_gpiod set but num_resetclks = 0, a pending event check can lead to memset overflowing to SIZE_MAX and corrupting the heap. The fix involves returning 0 immediately when neither rdy_gpiod nor has_registers is set, and adding an explicit data_read_len == 0 guard after the pending event check.
Defensive priority
Defenders should prioritize verifying and applying patches for Linux kernel versions affected by this vulnerability, particularly for systems using the ad_sigma_delta driver. They should also review device configurations and assess exposure based on device types and kernel versions.
Recommended defensive actions
- Verify and apply Linux kernel patches for CVE-2026-64502
- Review device configurations for ad_sigma_delta driver usage
- Assess exposure based on device types and kernel versions
- Monitor system logs for potential exploitation attempts
- Track exceptions and retest remediated assets
- Review compensating controls for exposed systems
- Plan vendor-supported updates or mitigations through normal change control
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected components. The Linux kernel patch references are also provided. Defenders should verify Linux kernel versions, review device configurations for ad_sigma_delta driver usage, and assess exposure based on device types and kernel versions. The patch addresses a vulnerability in the Linux kernel's iio: adc: ad_sigma_delta driver that can lead to heap corruption and data corruption. The fix involves returning 0 immediately
Sources and references
Verified primary and authoritative sources
-
CVE-2026-64502 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-64502
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-64502 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64502
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/3394e0b3328422431cadaf314fa58d3717ed4936
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/3bceb26dfaf7ba805b459e41c1d0ba916862dade
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/91bc6767a4f55dc470d8a56b55b9f2ea09094efe
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.