CVE-2026-97926

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.2%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:

ufs: validate cylinder group metadata before caching it

ufs_read_cylinder() copies the cylinder group index and the rotor positions straight from the on-disk group and caches them without any check:

ucpi->c_cgx = fs32_to_cpu(sb, ucg->cg_cgx); ucpi->c_rotor = fs32_to_cpu(sb, ucg->cg_rotor); ucpi->c_frotor = fs32_to_cpu(sb, ucg->cg_frotor); ucpi->c_irotor = fs32_to_cpu(sb, ucg->cg_irotor);

They are then used as indices during allocation and free:

  • c_cgx indexes the cylinder summary array as
UFS_SB(sb)->fs_cs(ucpi->c_cgx), so a value past s_ncg writes a 32 bit count outside the s_csp allocation.
  • c_frotor becomes a bitmap scan start, start = c_frotor >> 3, and
then length = ((s_fpg + 7) >> 3) - start. A start beyond the block bitmap wraps the unsigned length to a huge value, so ubh_scanc() walks far past the cylinder group buffers. c_irotor drives the inode bitmap the same way.

A crafted image can set any of these freely, turning an ordinary allocation into an out of bounds access.

Reject a cylinder group whose recorded index does not match the group being read, or whose rotors fall outside the group, before the metadata is cached. Valid filesystems keep cg_cgx equal to the group number and the rotors within the group, so only malformed images are rejected.

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.2%
EPSS %ILE
3rd
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

ufs: validate cylinder group metadata before caching it - kernel/git/stable/linux.git - Linux kernel stable tree

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

ufs: validate cylinder group metadata before caching it - kernel/git/stable/linux.git - Linux kernel stable tree

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

ufs: validate cylinder group metadata before caching it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87b12dc360a002eb2d498aa4f01e84347019612d
generic

ufs: validate cylinder group metadata before caching it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5902a95066883cf96fa15b2680694fc5dd0c7d11

Vendor Advisories for CVE-2026-97926(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
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 42× in last 7d / 61× 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 01:50 UTCEG score recompute
  2. 2026-10-05 01:50 UTCVendor advisory
  3. 2026-10-05 01:50 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 13:00 UTCVendor advisory
  6. 2026-10-04 13:00 UTCGHSA enrichment
  7. 2026-10-04 00:08 UTCEG score recompute
  8. 2026-10-04 00:08 UTCVendor advisory
  9. 2026-10-04 00:08 UTCGHSA enrichment
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-03 11:19 UTCEG score recompute
  12. 2026-10-03 11:19 UTCVendor advisory
  13. 2026-10-03 11:19 UTCGHSA enrichment
  14. 2026-10-03 04:51 UTCEG score recompute
  15. 2026-10-03 04:51 UTCVendor advisory
  16. 2026-10-03 04:51 UTCGHSA enrichment
  17. 2026-10-02 17:57 UTCEPSS rescore
  18. 2026-10-02 16:01 UTCVendor advisory
  19. 2026-10-02 16:01 UTCGHSA enrichment
  20. 2026-10-02 03:09 UTCEG score recompute
  21. 2026-10-02 03:09 UTCVendor advisory
  22. 2026-10-02 03:09 UTCGHSA enrichment
  23. 2026-10-01 19:51 UTCEPSS rescore
  24. 2026-10-01 14:20 UTCVendor advisory
  25. 2026-10-01 14:20 UTCGHSA enrichment
Show 36 more
  1. 2026-10-01 01:31 UTCEG score recompute
  2. 2026-10-01 01:31 UTCVendor advisory
  3. 2026-10-01 01:31 UTCGHSA enrichment
  4. 2026-09-30 15:04 UTCEPSS rescore
  5. 2026-09-30 12:42 UTCVendor advisory
  6. 2026-09-30 12:42 UTCGHSA enrichment
  7. 2026-09-29 23:50 UTCEG score recompute
  8. 2026-09-29 23:50 UTCVendor advisory
  9. 2026-09-29 23:50 UTCGHSA enrichment
  10. 2026-09-29 09:10 UTCEG score recompute
  11. 2026-09-29 09:10 UTCVendor advisory
  12. 2026-09-29 09:10 UTCGHSA enrichment
  13. 2026-09-28 20:21 UTCEG score recompute
  14. 2026-09-28 20:21 UTCVendor advisory
  15. 2026-09-28 20:21 UTCGHSA enrichment
  16. 2026-09-28 13:52 UTCEPSS rescore
  17. 2026-09-28 13:52 UTCEPSS rescore
  18. 2026-09-28 07:32 UTCVendor advisory
  19. 2026-09-28 07:32 UTCGHSA enrichment
  20. 2026-09-27 18:43 UTCEG score recompute
  21. 2026-09-27 18:43 UTCGHSA enrichment
  22. 2026-09-27 13:49 UTCEPSS rescore
  23. 2026-09-27 05:54 UTCGHSA enrichment
  24. 2026-09-26 17:04 UTCEG score recompute
  25. 2026-09-26 17:04 UTCGHSA enrichment
  26. 2026-09-26 15:59 UTCEPSS rescore
  27. 2026-09-26 04:15 UTCEG score recompute
  28. 2026-09-26 04:15 UTCGHSA enrichment
  29. 2026-09-25 15:24 UTCEG score recompute
  30. 2026-09-25 15:24 UTCGHSA enrichment
  31. 2026-09-25 14:52 UTCEG score recompute▲ 7.00
  32. 2026-09-25 14:52 UTCGHSA enrichment
  33. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 7 · severity → HIGH
  34. 2026-09-25 11:30 UTCNVD update
  35. 2026-09-25 10:35 UTCEG score recompute
  36. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97926?
CVE-2026-97926 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: ufs: validate cylinder group metadata before caching it ufsreadcylinder() copies the cylinder group index and the rotor positions straight from the on-disk group and caches them without any check: ucpi->ccgx = fs32tocpu(sb,…
When was CVE-2026-97926 disclosed?
CVE-2026-97926 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-97926 actively exploited?
CVE-2026-97926 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97926?
CVE-2026-97926 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-97926?
No fix for CVE-2026-97926 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-97926 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-97926

Explore →

Is Your Infrastructure Affected by CVE-2026-97926?

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