CVE-2026-90260

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: 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: zoned: don't clobber the extent buffer when zeroing it out

On a zoned filesystem a freed-but-still-dirty tree block is written out as zeros (EXTENT_BUFFER_ZONED_ZEROOUT) only to keep the zone write pointer advancing. btree_csum_one_bio() implemented this by memzeroing the extent buffer's own folios before submission.

That destroys the in-memory buffer while it may still be referenced. In particular btrfs_free_tree_block() can run on it afterwards and reads the header to add a delayed reference; once the header has been zeroed it frees bytenr 0 and corrupts the extent tree (the btrfs_header_bytenr(buf) != 0 ASSERT in btrfs_free_tree_block(), or an "unable to find ref" abort). It is flaky and reproduces under fsstress, e.g. generic/461 and generic/013.

Write the zeros to disk from the shared zero page instead and leave the extent buffer content untouched, so any later reference - including the delayed reference from btrfs_free_tree_block() - still sees a valid header. end_bbio_meta_write() now clears writeback on the buffer's own folios, as the bio no longer carries them.

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
37
EG Risk 37/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
Severity71% × 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.2%
EPSS %ILE
5th
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 17, 2026

Last Modified

September 18, 2026

Advisory Details (3)

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

btrfs: zoned: don't clobber the extent buffer when zeroing it out - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: zoned: don't clobber the extent buffer when zeroing it out - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98e3747587f9f87f010d8d7e55786216249a94af
generic

btrfs: zoned: don't clobber the extent buffer when zeroing it out - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92484ad014f2e2b0e0e7bbc1610951e978cf557c

Vendor Advisories for CVE-2026-90260(1)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 25× in last 7d / 70× 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-04 23:22 UTCEPSS rescore
  2. 2026-10-04 22:54 UTCGHSA enrichment
  3. 2026-10-04 11:13 UTCGHSA enrichment
  4. 2026-10-03 23:32 UTCEG score recompute
  5. 2026-10-03 23:32 UTCGHSA enrichment
  6. 2026-10-03 11:51 UTCGHSA enrichment
  7. 2026-10-02 23:59 UTCEG score recompute
  8. 2026-10-02 23:59 UTCGHSA enrichment
  9. 2026-10-02 12:18 UTCGHSA enrichment
  10. 2026-10-02 00:09 UTCEG score recompute
  11. 2026-10-02 00:08 UTCGHSA enrichment
  12. 2026-10-01 19:51 UTCEPSS rescore
  13. 2026-10-01 12:19 UTCGHSA enrichment
  14. 2026-10-01 00:36 UTCEG score recompute
  15. 2026-10-01 00:36 UTCGHSA enrichment
  16. 2026-09-30 15:04 UTCEPSS rescore
  17. 2026-09-30 12:27 UTCGHSA enrichment
  18. 2026-09-30 00:44 UTCEG score recompute
  19. 2026-09-30 00:44 UTCGHSA enrichment
  20. 2026-09-29 12:16 UTCGHSA enrichment
  21. 2026-09-29 00:35 UTCEG score recompute
  22. 2026-09-29 00:35 UTCGHSA enrichment
  23. 2026-09-28 13:52 UTCEPSS rescore
  24. 2026-09-28 13:52 UTCEPSS rescore
  25. 2026-09-28 12:54 UTCGHSA enrichment
Show 45 more
  1. 2026-09-28 01:13 UTCEG score recompute
  2. 2026-09-28 01:13 UTCGHSA enrichment
  3. 2026-09-27 13:49 UTCEPSS rescore
  4. 2026-09-27 13:32 UTCGHSA enrichment
  5. 2026-09-27 01:51 UTCEG score recompute
  6. 2026-09-27 01:51 UTCGHSA enrichment
  7. 2026-09-26 15:59 UTCEPSS rescore
  8. 2026-09-26 14:04 UTCGHSA enrichment
  9. 2026-09-26 02:18 UTCEG score recompute
  10. 2026-09-26 02:18 UTCGHSA enrichment
  11. 2026-09-25 14:34 UTCGHSA enrichment
  12. 2026-09-25 02:52 UTCGHSA enrichment
  13. 2026-09-24 15:10 UTCEG score recompute
  14. 2026-09-24 15:10 UTCGHSA enrichment
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-24 03:29 UTCEG score recompute
  17. 2026-09-24 03:29 UTCGHSA enrichment
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-23 15:48 UTCGHSA enrichment
  20. 2026-09-23 04:08 UTCGHSA enrichment
  21. 2026-09-22 16:27 UTCEG score recompute
  22. 2026-09-22 16:27 UTCGHSA enrichment
  23. 2026-09-22 16:01 UTCEPSS rescore
  24. 2026-09-22 04:38 UTCEG score recompute
  25. 2026-09-22 04:38 UTCGHSA enrichment
  26. 2026-09-21 21:09 UTCEPSS rescore
  27. 2026-09-21 16:56 UTCGHSA enrichment
  28. 2026-09-21 04:56 UTCEG score recompute
  29. 2026-09-21 04:56 UTCGHSA enrichment
  30. 2026-09-20 20:16 UTCEPSS rescore
  31. 2026-09-20 17:15 UTCGHSA enrichment
  32. 2026-09-20 05:34 UTCGHSA enrichment
  33. 2026-09-19 17:53 UTCEG score recompute
  34. 2026-09-19 17:53 UTCGHSA enrichment
  35. 2026-09-19 06:12 UTCEG score recompute
  36. 2026-09-19 06:12 UTCGHSA enrichment
  37. 2026-09-18 19:28 UTCEPSS rescore
  38. 2026-09-18 18:30 UTCEG score recompute
  39. 2026-09-18 18:30 UTCGHSA enrichment
  40. 2026-09-18 18:03 UTCEG score recompute▲ 7.10
  41. 2026-09-18 18:03 UTCGHSA enrichment
  42. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  43. 2026-09-17 17:24 UTCNVD update
  44. 2026-09-17 16:35 UTCEG score recompute
  45. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-90260?
CVE-2026-90260 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: don't clobber the extent buffer when zeroing it out On a zoned filesystem a freed-but-still-dirty tree block is written out as zeros (EXTENTBUFFERZONED_ZEROOUT) only to keep the zone write pointer advancing.…
When was CVE-2026-90260 disclosed?
CVE-2026-90260 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90260 actively exploited?
CVE-2026-90260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90260?
CVE-2026-90260 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90260?
No fix for CVE-2026-90260 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-90260 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-90260

Explore →

Is Your Infrastructure Affected by CVE-2026-90260?

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

Book a Demo →Browse All CVEs