CVE-2026-80638

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

In the Linux kernel, the following vulnerability has been resolved:

ocfs2: fix out-of-bounds write in ocfs2_remove_refcount_extent

[BUG] Unlinking a refcounted file whose refcount tree has leaf blocks triggers a fortify panic due to an out-of-bounds write.

[CAUSE] When the last leaf block is removed from a refcount tree, ocfs2_remove_refcount_extent() converts the root back to leaf mode with a bulk memset on &rb->rf_records. rf_records sits in an anonymous union with rf_list. rf_list.l_tree_depth aliases rf_records.rl_count, and is 0 for a single-level tree. With rl_count equal to 0, the memset writes past the 16-byte declared size of rf_records, which the fortify checker catches.

[FIX] Replace the bulk memset on &rb->rf_records with a correctly-bounded memset on rl_recs[] alone, after setting rl_count to the correct value.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (2)

Auto-updated Aug 29, 2026
No patch confirmed yet.
generic

ocfs2: fix out-of-bounds write in ocfs2_remove_refcount_extent - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1ec3cca2d8b6b9ff6584ca626d4c8918bbf48d44
generic

ocfs2: fix out-of-bounds write in ocfs2_remove_refcount_extent - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-80638(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 14× 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-08-30 05:15 UTCEG score recompute
  2. 2026-08-30 05:15 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 18:21 UTCEG score recompute
  5. 2026-08-29 18:21 UTCGHSA enrichment
  6. 2026-08-29 07:26 UTCEG score recompute
  7. 2026-08-29 07:26 UTCGHSA enrichment
  8. 2026-08-29 06:36 UTCEG score recompute 8.80
  9. 2026-08-29 06:36 UTCGHSA enrichment
  10. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  11. 2026-08-28 21:42 UTCEPSS rescore
  12. 2026-08-28 08:20 UTCNVD update
  13. 2026-08-28 07:34 UTCEG score recompute
  14. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80638?
CVE-2026-80638 is a high vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix out-of-bounds write in ocfs2removerefcount_extent [BUG] Unlinking a refcounted file whose refcount tree has leaf blocks triggers a fortify panic due to an out-of-bounds write. [CAUSE] When the last leaf block is removed…
When was CVE-2026-80638 disclosed?
CVE-2026-80638 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80638 actively exploited?
CVE-2026-80638 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.5% of all scored CVEs.
What is the CVSS score of CVE-2026-80638?
CVE-2026-80638 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-80638?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80638, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80638

Explore →

Is Your Infrastructure Affected by CVE-2026-80638?

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