CVE-2026-98083

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-09-25. A secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.0EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.0Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
7.0
EG Score
7.0HIGHhigh confidence
EG Risk
36
EG Risk 36/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

October 3, 2026

Advisory Details (4)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

btrfs: fix transaction use-after-free in raid stripe insertion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a8813a923f9e43f788b357fb55c35f7f6ed6f98c
generic

btrfs: fix transaction use-after-free in raid stripe insertion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b7b94923b3b5774d85a2a7c8d6eb9e3e0ef66685
generic

btrfs: fix transaction use-after-free in raid stripe insertion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2fbfd02bdfe12b20bd3cc7a3190fb32e3f7072f5
generic

btrfs: fix transaction use-after-free in raid stripe insertion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b185bdf30313e213fa1c887fe22fc3d513c061d9

Vendor Advisories for CVE-2026-98083(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (180 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 48× in last 7d / 66× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 00:40 UTCEG score recompute
  2. 2026-10-05 00:40 UTCVendor advisory
  3. 2026-10-05 00:40 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 12:15 UTCVendor advisory
  6. 2026-10-04 12:15 UTCGHSA enrichment
  7. 2026-10-03 23:52 UTCEG score recompute
  8. 2026-10-03 23:52 UTCVendor advisory
  9. 2026-10-03 23:52 UTCGHSA enrichment
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-03 11:27 UTCEG score recompute
  12. 2026-10-03 11:27 UTCVendor advisory
  13. 2026-10-03 11:27 UTCGHSA enrichment
  14. 2026-10-03 11:12 UTCEG score recompute
  15. 2026-10-03 11:12 UTCVendor advisory
  16. 2026-10-03 11:12 UTCGHSA enrichment
  17. 2026-10-03 04:43 UTCEG score recompute
  18. 2026-10-03 04:43 UTCVendor advisory
  19. 2026-10-03 04:43 UTCGHSA enrichment
  20. 2026-10-02 17:57 UTCEPSS rescore
  21. 2026-10-02 16:18 UTCVendor advisory
  22. 2026-10-02 16:17 UTCGHSA enrichment
  23. 2026-10-02 16:17 UTCVendor advisory
  24. 2026-10-02 16:17 UTCVendor advisory
  25. 2026-10-02 16:17 UTCGHSA enrichment
Show 41 more
  1. 2026-10-02 16:17 UTCGHSA enrichment
  2. 2026-10-02 03:52 UTCEG score recompute
  3. 2026-10-02 03:52 UTCVendor advisory
  4. 2026-10-02 03:52 UTCGHSA enrichment
  5. 2026-10-01 19:51 UTCEPSS rescore
  6. 2026-10-01 15:25 UTCVendor advisory
  7. 2026-10-01 15:25 UTCGHSA enrichment
  8. 2026-10-01 02:59 UTCEG score recompute
  9. 2026-10-01 02:59 UTCVendor advisory
  10. 2026-10-01 02:59 UTCGHSA enrichment
  11. 2026-09-30 15:04 UTCEPSS rescore
  12. 2026-09-30 14:34 UTCVendor advisory
  13. 2026-09-30 14:34 UTCGHSA enrichment
  14. 2026-09-30 07:16 UTCVendor advisory
  15. 2026-09-30 07:16 UTCGHSA enrichment
  16. 2026-09-29 18:51 UTCEG score recompute
  17. 2026-09-29 18:51 UTCVendor advisory
  18. 2026-09-29 18:51 UTCGHSA enrichment
  19. 2026-09-29 06:23 UTCEG score recompute
  20. 2026-09-29 06:23 UTCVendor advisory
  21. 2026-09-29 06:23 UTCGHSA enrichment
  22. 2026-09-28 17:59 UTCVendor advisory
  23. 2026-09-28 17:59 UTCGHSA enrichment
  24. 2026-09-28 05:31 UTCGHSA enrichment
  25. 2026-09-27 17:07 UTCEG score recompute
  26. 2026-09-27 17:07 UTCGHSA enrichment
  27. 2026-09-27 13:49 UTCEPSS rescore
  28. 2026-09-27 04:43 UTCGHSA enrichment
  29. 2026-09-26 16:17 UTCEG score recompute
  30. 2026-09-26 16:16 UTCGHSA enrichment
  31. 2026-09-26 15:59 UTCEPSS rescore
  32. 2026-09-26 03:51 UTCEG score recompute
  33. 2026-09-26 03:50 UTCGHSA enrichment
  34. 2026-09-25 15:23 UTCEG score recompute
  35. 2026-09-25 15:23 UTCGHSA enrichment
  36. 2026-09-25 14:51 UTCEG score recompute▲ 7.00
  37. 2026-09-25 14:51 UTCGHSA enrichment
  38. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 7 · severity → HIGH
  39. 2026-09-25 11:30 UTCNVD update
  40. 2026-09-25 10:27 UTCEG score recompute
  41. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98083?
CVE-2026-98083 is a high vulnerability published on September 25, 2026. 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, btrfsinsertoneraidextent() aborts and ends the transaction before returning -ENOMEM. btrfsfinishone_ordered(), the…
When was CVE-2026-98083 disclosed?
CVE-2026-98083 was first published on September 25, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-98083 actively exploited?
CVE-2026-98083 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98083?
CVE-2026-98083 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-98083?
No fix for CVE-2026-98083 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-98083 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-98083

Explore →

Is Your Infrastructure Affected by CVE-2026-98083?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs