CVE-2026-97548

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
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.8Exploit: 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:

xfs: fix the rtrmap and rtrefcount _maxlevels_ondisk functions

The _maxlevels_ondisk functions are used to compute the size of in-memory btree cursors for each btree type. Unfortunately, LOLLM noticed that the rtrmap and rtrefcount versions of these functions forget to account for the inode root, which means that we could access beyond the end of the cursor given a sufficiently large btree. Fix this.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/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
Severity78% × 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 25, 2026

Last Modified

September 25, 2026

Advisory Details (3)

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

xfs: fix the rtrmap and rtrefcount _maxlevels_ondisk functions - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfs: fix the rtrmap and rtrefcount _maxlevels_ondisk functions - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/84316cb25af95a60e655ccc8fe646bb5ad631b71
generic

xfs: fix the rtrmap and rtrefcount _maxlevels_ondisk functions - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/108114437915e61e8f88d1cbcc442c3f886a347e

Vendor Advisories for CVE-2026-97548(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-97548?
CVE-2026-97548 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: xfs: fix the rtrmap and rtrefcount maxlevelsondisk functions The maxlevelsondisk functions are used to compute the size of in-memory btree cursors for each btree type. Unfortunately, LOLLM noticed that the rtrmap and rtrefcount…
When was CVE-2026-97548 disclosed?
CVE-2026-97548 was first published on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97548 actively exploited?
CVE-2026-97548 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-97548?
CVE-2026-97548 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97548?
No fix for CVE-2026-97548 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-97548 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-97548

Explore →

Is Your Infrastructure Affected by CVE-2026-97548?

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