Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98669iio: buffer: serialize buffer teardown with mode claims

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().

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected a9c471892d75847671a246619c2148578f22bbc6 – < 261f54966ebf45ced5fe5e1fe5119c6c44e140ab
    • affected 7bca0af538a49dacb1470f233be0676bdc09605b – < cebbecb26d22368440c4779f8275d790cf347177
    • affected 0a8565425afd8ba0e1a0ea73e21da119ee6dacea – < 6a728408ff522b749c2a3c7e68f44e861fa0dbfb
    • affected 0a8565425afd8ba0e1a0ea73e21da119ee6dacea – < 89f3852a28fcf7bab599280cb082baa0675536db
    • affected 0a8565425afd8ba0e1a0ea73e21da119ee6dacea – < b466db9e68b4741af85f6c017e2bb0a2f025053f
    • affected 0a8565425afd8ba0e1a0ea73e21da119ee6dacea – < e63188d77e10c0951bf67da6c295f768fd1abf4b
    • affected 0a8565425afd8ba0e1a0ea73e21da119ee6dacea – < 84bb0fc46ccf6a545b8fdf57cda83770186ed8dd
    • affected 5.15.137 – < 5.15.224
    • affected 6.1.60 – < 6.1.191
  • Linux · Linux

    • affected 6.2
    • unaffected < 6.2
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98669 badge
[![CVE-2026-98669](https://cveledger.app/badge/CVE-2026-98669.svg)](https://cveledger.app/cve/CVE-2026-98669)

Record last updated .