CVE-2026-72164

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.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: 7.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: avoid moving extents to occupied clusters

For non-auto OCFS2_IOC_MOVE_EXT operations, userspace supplies a physical me_goal. ocfs2_move_extent() initializes new_phys_cpos from that goal and expects ocfs2_probe_alloc_group() to replace it with a free run in the target block group.

The probe currently leaves *phys_cpos unchanged if the scan reaches the end of the group without finding a free run. An occupied goal at the last bit can therefore survive the probe and be passed to __ocfs2_move_extent(), which copies file data into a cluster still owned by another inode before the bitmap is updated.

When the probe does find a free run, it also subtracts move_len from the ending bit. The start of an N-bit run ending at i is i - N + 1, so the current calculation can report the bit immediately before the free run.

Clear *phys_cpos before scanning and use the correct free-run start. Callers already treat a zero result as -ENOSPC, so failed probes no longer continue with an occupied caller-controlled goal.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

ocfs2: avoid moving extents to occupied clusters - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2: avoid moving extents to occupied clusters - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2: avoid moving extents to occupied clusters - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d1953d3aeb4a7f6623083e1839068ee1c157db2
generic

ocfs2: avoid moving extents to occupied clusters - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35486b291b8fbde6c4d0b1c79e565c6260d3329d
generic

ocfs2: avoid moving extents to occupied clusters - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3112afebf2a76e522fbaabcbb0c47aafbdc35932
generic

ocfs2: avoid moving extents to occupied clusters - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/22920541c35a9f23f219038ba5874c843a7c4419
generic

ocfs2: avoid moving extents to occupied clusters - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19f7b04924b20b81dabbeed19d5542792ba5b6d6
generic

ocfs2: avoid moving extents to occupied clusters - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d0c5c17b18bdbc592ac26ab4d1de7e3dbf9be1e

Vendor Advisories for CVE-2026-72164(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 31× in last 7d / 31× 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-21 01:53 UTCEG score recompute
  2. 2026-08-21 01:53 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 12:48 UTCGHSA enrichment
  5. 2026-08-19 23:45 UTCEG score recompute
  6. 2026-08-19 23:45 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 10:41 UTCGHSA enrichment
  9. 2026-08-18 21:37 UTCEG score recompute
  10. 2026-08-18 21:37 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 08:32 UTCGHSA enrichment
  14. 2026-08-17 19:25 UTCEG score recompute
  15. 2026-08-17 19:25 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 06:21 UTCEG score recompute
  18. 2026-08-17 06:21 UTCGHSA enrichment
  19. 2026-08-17 06:00 UTCEG score recompute 7.80
  20. 2026-08-17 06:00 UTCGHSA enrichment
  21. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  22. 2026-08-17 05:32 UTCEG score recompute
  23. 2026-08-17 05:32 UTCGHSA enrichment
  24. 2026-08-17 05:25 UTCMITRE cvelistV5
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 6 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 02:15 UTCEPSS rescore
  3. 2026-08-15 06:42 UTCGHSA enrichment
  4. 2026-08-15 06:23 UTCNVD update
  5. 2026-08-15 06:11 UTCEG score recompute
  6. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72164?
CVE-2026-72164 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ocfs2: avoid moving extents to occupied clusters For non-auto OCFS2IOCMOVE_EXT operations, userspace supplies a physical megoal. ocfs2moveextent() initializes newphys_cpos from that goal and expects ocfs2probealloc_group() to…
When was CVE-2026-72164 disclosed?
CVE-2026-72164 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72164 actively exploited?
CVE-2026-72164 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 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72164?
CVE-2026-72164 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72164?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72164, 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-72164

Explore →

Is Your Infrastructure Affected by CVE-2026-72164?

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