Skip to content
Threat Brief

← All advisories

CVE-2026-64501

High 7.1No known exploitationFix available

iio: adc: ad_sigma_delta: fix CS held asserted and state leaks

Record last updated

CVSS score

7.1

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: iio: adc: ad_sigma_delta: fix CS held asserted and state leaks In ad_sigma_delta_single_conversion(), set_mode(AD_SD_MODE_IDLE) and disable_one() were called from the out: block while keep_cs_asserted was still true. This caused any SPI transfer issued by those callbacks to carry cs_change=1, leaving CS permanently asserted after the conversion. Fix by moving both calls into the out_unlock: block, after keep_cs_asserted is cleared, matching the pattern already used in ad_sd_calibrate(). In the error path of ad_sd_buffer_postenable(), if an operation fails after set_mode(AD_SD_MODE_CONTINUOUS) has already succeeded (e.g. spi_offload_trigger_enable()), the device is left in continuous conversion mode with CS physically asserted. Additionally, bus_locked remaining true after spi_bus_unlock() causes subsequent SPI operations to call spi_sync_locked() without the bus lock actually held, allowing concurrent SPI access. Fix the error path by clearing keep_cs_asserted first, then calling set_mode(AD_SD_MODE_IDLE) to revert the device mode and deassert CS, then clearing bus_locked before releasing the bus. For devices that implement neither set_mode nor disable_one (such as MAX11205, which has no physical CS pin), no SPI transfer is issued during cleanup and the cs_change flag has no effect on any physical line.

Weakness: CWE-401

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

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 132d44dc6966c1cf841ffe0f6f048165687e870b before c72da0688575e5ef39c36bb44fed53aa18f8ae65c72da0688575e5ef39c36bb44fed53aa18f8ae65CVE Program
LinuxLinuxfrom 132d44dc6966c1cf841ffe0f6f048165687e870b before c313bb7c38855e94ceef939d152dd75e5a904b5fc313bb7c38855e94ceef939d152dd75e5a904b5fCVE Program
LinuxLinuxfrom 132d44dc6966c1cf841ffe0f6f048165687e870b before f1de829ee87a1198d3465493ce430d36c5fa029cf1de829ee87a1198d3465493ce430d36c5fa029cCVE Program
LinuxLinux6.14Not documentedCVE Program
linuxlinux_kernelfrom 6.14 before 6.18.396.18.39NIST NVD
linuxlinux_kernelfrom 6.19 before 7.1.47.1.4NIST NVD
LinuxLinux (unaffected)from 6.18.39 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.1.4 up to and including 7.1.*Not documentedCVE Program
LinuxLinux (unaffected)7.2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.14Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by NVD (reference tagged Patch)

    Source: NVD (reference tagged Patch) (opens in a new tab)

Vendor guidance and references