Answer in brief
CVE-2026-98669 records a Unknown severity vulnerability in iio: buffer: serialize buffer teardown with mode claims. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0a8565425afd8ba0e1a0ea73e21da119ee6dacea <89f3852a28fcf7bab599280cb082baa0675536db || >=0a8565425afd8ba0e1a0ea73e21da119ee6dacea <b466db9e68b4741af85f6c017e2bb0a2f025053f || >=0a8565425afd8ba0e1a0ea73e21da119ee6dacea <e63188d77e10c0951bf67da6c295f768fd1abf4b || >=0a8565425afd8ba0e1a0ea73e21da119ee6dacea <84bb0fc46ccf6a545b8fdf57cda83770186ed8dd || a9c471892d75847671a246619c2148578f22bbc6 || 7bca0af538a49dacb1470f233be0676bdc09605b || >=5.15.137 <5.16 || >=6.1.60 <6.2 | 89f3852a28fcf7bab599280cb082baa0675536db, b466db9e68b4741af85f6c017e2bb0a2f025053f, e63188d77e10c0951bf67da6c295f768fd1abf4b, 84bb0fc46ccf6a545b8fdf57cda83770186ed8dd, 5.16, 6.2 |
| Linux/Linuxgeneric | 6.2 | Not reported |
| Linux/Linuxgeneric | >=0a8565425afd8ba0e1a0ea73e21da119ee6dacea <6a728408ff522b749c2a3c7e68f44e861fa0dbfb || >=0a8565425afd8ba0e1a0ea73e21da119ee6dacea <89f3852a28fcf7bab599280cb082baa0675536db || >=0a8565425afd8ba0e1a0ea73e21da119ee6dacea <b466db9e68b4741af85f6c017e2bb0a2f025053f || >=0a8565425afd8ba0e1a0ea73e21da119ee6dacea <e63188d77e10c0951bf67da6c295f768fd1abf4b || >=0a8565425afd8ba0e1a0ea73e21da119ee6dacea <84bb0fc46ccf6a545b8fdf57cda83770186ed8dd || a9c471892d75847671a246619c2148578f22bbc6 || 7bca0af538a49dacb1470f233be0676bdc09605b || >=5.15.137 <5.16 || >=6.1.60 <6.2 | 6a728408ff522b749c2a3c7e68f44e861fa0dbfb, 89f3852a28fcf7bab599280cb082baa0675536db, b466db9e68b4741af85f6c017e2bb0a2f025053f, e63188d77e10c0951bf67da6c295f768fd1abf4b, 84bb0fc46ccf6a545b8fdf57cda83770186ed8dd, 5.16, 6.2 |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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().
Quoted source text, attributed separately from HOL analysis.