Live › vulnerability › CVE-2026-98669
Go to dashboardIn the Linux kernel's Industrial I/O (IIO) subsystem, unregistering a device disables and deactivates its buffers without holding the mode lock, so buffer state can change while a buffer-mode claim is held. The sources do not describe a concrete attacker-reachable impact.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with IIO sensor or ADC drivers loaded, where devices can be unregistered while buffers are in use. Systems without IIO hardware or drivers are unlikely to be affected. The sources do not say more.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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().
This page as .md · .json · in your agent: get_signal("CVE-2026-98669")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.