CVE-2026-98669
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().
Affected versions
Linux kernel versions
5.15.137,
6.1.60,
6.2
and later are affected. Fixed in
6.12.113,
6.18.56,
7.2.10,
7.3
and their respective stable series.
References
4 totalFrequently asked questions
-
What is CVE-2026-98669?
CVE-2026-98669 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.15.137 onward and has been patched in 6.12.113, 6.18.56, 7.2.10 and others. CVE-2026-98669 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-98669?
Yes. CVE-2026-98669 has been patched. Fixed versions include 6.12.113, 6.18.56, 7.2.10 and others. If you are running Linux kernel 5.15.137 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-98669 actively exploited?
No. CVE-2026-98669 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.