CVE-2026-64501

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.1 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=*, 6.14, <c313bb7c38855e94ceef939d152dd75e5a904b5f, <=6.18.*, <6.14, 6.18.39, <f1de829ee87a1198d3465493ce430d36c5fa029c, 132d44dc6966c1cf841ffe0f6f048165687e870b, 0, <c72da0688575e5ef39c36bb44fed53aa18f8ae65, 7.2, <=7.1.*, 7.1.4

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.

Gravité et risque d'exploitation

CVE-2026-64501 obtient un score CVSS de 7.1/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.17 %, ce qui la place devant 5.9 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=*, 6.14, <c313bb7c38855e94ceef939d152dd75e5a904b5f, <=6.18.*, <6.14, 6.18.39, <f1de829ee87a1198d3465493ce430d36c5fa029c, 132d44dc6966c1cf841ffe0f6f048165687e870b, 0, <c72da0688575e5ef39c36bb44fed53aa18f8ae65, 7.2, <=7.1.*, 7.1.4) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références