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-98091btrfs: detach failed sprout device from transaction update list

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: detach failed sprout device from transaction update list When creating the first metadata chunk for a sprout filesystem, create_chunk() adds the new device to the transaction dev_update_list through device->post_commit_list. If the subsequent system chunk creation fails, btrfs_init_new_device() aborts the transaction and releases the device while post_commit_list is still linked. This triggers a warning in btrfs_free_device() and leaves the transaction list referencing freed memory. Detach the device while holding chunk_mutex before releasing it.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 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

CVSS scores of CVE-2026-98091, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected bbbf7243d62d8be73b7ef60721c127b36b2d523e – < 2a57fb1d5ce8f316b81bbb60e6df245ebc816ffc
    • affected bbbf7243d62d8be73b7ef60721c127b36b2d523e – < 86eff3052054e8f3b059b2d5845b6dcca021f20c
    • affected bbbf7243d62d8be73b7ef60721c127b36b2d523e – < 63bfa52eb3289517aa82cb90e1189385873aae21
    • affected bbbf7243d62d8be73b7ef60721c127b36b2d523e – < 7fe9dfbca43464baa8f050447a4837587b18adec
    • affected bbbf7243d62d8be73b7ef60721c127b36b2d523e – < e9e7e37afa85db770e6084360b21a21a8b3a583f
    • affected bbbf7243d62d8be73b7ef60721c127b36b2d523e – < 8b001df2b37ca022f710f3254fbb0bcd6d9e1bed
    • affected bbbf7243d62d8be73b7ef60721c127b36b2d523e – < 0ea6814bc0ff7cff443241bd34db9f0f828f3190
    • affected bbbf7243d62d8be73b7ef60721c127b36b2d523e – < c93b3c43df561cd9f592cee20ae058b563f9e5b6
  • Linux · Linux

    • affected 5.2
    • unaffected < 5.2
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .