Skip to main content
VulnerabilityPublished Updated

CVE-2026-98669: Linux kernel · iio: buffer: serialize buffer teardown with mode claims

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in e63188d77e10c0951bf67da6c295f768fd1abf4b : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in e63188d77e10c0951bf67da6c295f768fd1abf4b, b466db9e68b4741af85f6c017e2bb0a2f025053f, 89f3852a28fcf7bab599280cb082baa0675536db +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.15.137 <5.16
  • >=6.1.60 <6.2
Fixed in
  • e63188d77e10c0951bf67da6c295f768fd1abf4b
  • b466db9e68b4741af85f6c017e2bb0a2f025053f
  • 89f3852a28fcf7bab599280cb082baa0675536db
  • 84bb0fc46ccf6a545b8fdf57cda83770186ed8dd
  • 6a728408ff522b749c2a3c7e68f44e861fa0dbfb
  • 6.2
  • 5.16
LinuxLinuxAffected
  • =6.2
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: iio: buffer: serialize buffer teardown with mode claims Buffer-mode claims hold mlock to guarantee that the device remains in buffer mode until the claim is released. Normal buffer updates take info_exist_lock followed by mlock in iio_update_buffers(). However, iio_device_unregister() disables and deactivates all buffers without taking mlock. This can invalidate buffer state, including active_scan_mask, while a buffer-mode claim is held. Take mlock in iio_disable_all_buffers() so that unregister honors the mode-claim lifetime guarantee. The info_exist_lock -> mlock ordering matches iio_update_buffers().

References

Community reviews

Loading reviews…