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-98083btrfs: fix transaction use-after-free in raid stripe insertion

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix transaction use-after-free in raid stripe insertion If allocation of a RAID stripe extent fails, btrfs_insert_one_raid_extent() aborts and ends the transaction before returning -ENOMEM. btrfs_finish_one_ordered(), the production caller through btrfs_insert_raid_extent(), still owns the transaction handle. It handles the error by aborting the transaction and then reaches the common exit path, which ends the transaction again. The premature end can free the handle and drop its transaction reference. Transaction cleanup can then free the transaction before the caller's second abort accesses the handle and transaction, resulting in use-after-free. Keep the abort at the failure site, but let the caller's common exit path end the transaction once, after it has finished using both objects.

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-98083, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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: High 7.0.

Affected products

  • Linux · Linux

    • affected ab69bf6f8970c09d3735c25094e9471d54365282 – < 089d9c45ea49ffffe55a8fe08d0ce2536626e90a
    • affected 02c372e1f016e5113217597ab37b399c4e407477 – < b185bdf30313e213fa1c887fe22fc3d513c061d9
    • affected 02c372e1f016e5113217597ab37b399c4e407477 – < 2fbfd02bdfe12b20bd3cc7a3190fb32e3f7072f5
    • affected 02c372e1f016e5113217597ab37b399c4e407477 – < b7b94923b3b5774d85a2a7c8d6eb9e3e0ef66685
    • affected 02c372e1f016e5113217597ab37b399c4e407477 – < a8813a923f9e43f788b357fb55c35f7f6ed6f98c
    • affected 6.6.130 – < 6.6.158
  • Linux · Linux

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

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .