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-98090btrfs: restore active device pointers after failed sprout

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: restore active device pointers after failed sprout btrfs_init_new_device() switches latest_dev and possibly s_bdev from the seed device to the new sprout device before creating the first writable chunks. If chunk creation or the subsequent sprout setup fails, the error path releases the new device without switching those pointers back. btrfs_show_devname() can then dereference the freed latest_dev and crash. Restore the active device pointers to the latest seed device before removing and releasing the failed sprout device.

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-98090, 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 (17 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 a6e7e218a4d6488d56727a7d9aee1b7e78c0c485 – < 46863a9f93186e620c70584f91c8d5d95da83eff
    • affected b7cb29e666fe79dda5dbe5f57fb7c92413bf161c – < 49179f13c04735c55fd0f43b03696c015b067137
    • affected b7cb29e666fe79dda5dbe5f57fb7c92413bf161c – < 0a0ee38ad6324ac1603079bb785f784191576bd5
    • affected b7cb29e666fe79dda5dbe5f57fb7c92413bf161c – < 2ee5c4bc11007c51f63f0c1be5d3f07f2b404ff7
    • affected b7cb29e666fe79dda5dbe5f57fb7c92413bf161c – < e127ac29a52134d0f4cba39d38e4b375deb3d1aa
    • affected b7cb29e666fe79dda5dbe5f57fb7c92413bf161c – < b79b4b29003690acfade8241998fc0104ef9c84c
    • affected b7cb29e666fe79dda5dbe5f57fb7c92413bf161c – < e0b54613aabeb8e9da597f23b90c6a03d0981986
    • affected 5.15.11 – < 5.15.222
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • 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

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .