CVE-2026-98669 iio: buffer: serialize buffer teardown with mode claims
A race condition in the Linux kernel IIO buffer subsystem allows local attackers to cause a denial of service by invalidating buffer state during device unregistration.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-98669?
CVE-2026-98669 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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().
Which versions are affected by CVE-2026-98669?
How do I fix CVE-2026-98669?
Apply the vendor's patch.
Is CVE-2026-98669 being exploited?
There is no known exploitation of CVE-2026-98669 in the wild and no public exploit code.
Sources
Also known as AZL-109329, BELL-CVE-2026-98669, DEBIAN-CVE-2026-98669, GHSA-h3hh-6rf8-4cq6, UBUNTU-CVE-2026-98669.