CVE-2026-98669
Last modified
CVE-2026-98669 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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().
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= a9c471892d75847671a246619c2148578f22bbc6, < 261f54966ebf45ced5fe5e1fe5119c6c44e140ab; >= 7bca0af538a49dacb1470f233be0676bdc09605b, < cebbecb26d22368440c4779f8275d790cf347177; >= 0a8565425afd8ba0e1a0ea73e21da119ee6dacea, < 6a728408ff522b749c2a3c7e68f44e861fa0dbfb; >= 0a8565425afd8ba0e1a0ea73e21da119ee6dacea, < 89f3852a28fcf7bab599280cb082baa0675536db; >= 0a8565425afd8ba0e1a0ea73e21da119ee6dacea, < b466db9e68b4741af85f6c017e2bb0a2f025053f; >= 0a8565425afd8ba0e1a0ea73e21da119ee6dacea, < e63188d77e10c0951bf67da6c295f768fd1abf4b; >= 0a8565425afd8ba0e1a0ea73e21da119ee6dacea, < 84bb0fc46ccf6a545b8fdf57cda83770186ed8dd; >= 5.15.137, < 5.15.224; >= 6.1.60, < 6.1.191 |
| Linux | Linux | 6.2 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98669?
How severe is CVE-2026-98669?
How do I fix CVE-2026-98669?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98663In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98664In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98665In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98666In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98667In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98668In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98670In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98671In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98672In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98673In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98674In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98675In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98669?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
