CVE-2026-72194

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.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:

fs/ntfs3: add depth limit to indx_find_buffer to prevent stack overflow

indx_find_buffer() recursively descends the B+ tree index with no depth limit. A crafted NTFS image with circular index node references causes unbounded recursion, overflowing the kernel stack and panicking the system.

This is reachable by mounting a malicious NTFS filesystem (e.g. from a USB drive via desktop automount) and deleting a file whose index entry triggers the rebalancing fallback path in indx_delete_entry().

Add a depth parameter and bail out with -EINVAL when it reaches the fnd->nodes array bound, matching the constraint already enforced by fnd_push() in indx_find().

The related function indx_find() was previously patched for a similar infinite-loop issue (commit 1732053c8a6b), but indx_find_buffer() was missed.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (7)

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

fs/ntfs3: add depth limit to indx_find_buffer to prevent stack overflow - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/ntfs3: add depth limit to indx_find_buffer to prevent stack overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/99031d4f63c785d2a985b6a4c64c4256f7117052
generic

fs/ntfs3: add depth limit to indx_find_buffer to prevent stack overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96fb64f9da86fd2dbd78fbe9d9e41ae27e12ce34
generic

fs/ntfs3: add depth limit to indx_find_buffer to prevent stack overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/908c9243ba309997b73cbda3e4c563d0fb345ee9
generic

fs/ntfs3: add depth limit to indx_find_buffer to prevent stack overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78612f478f9fadcec4f9b3b089970da67ffb47e9
generic

fs/ntfs3: add depth limit to indx_find_buffer to prevent stack overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65357a81f64cb3fbe13b4b937586755e4b3a072f
generic

fs/ntfs3: add depth limit to indx_find_buffer to prevent stack overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1ebd684b8f627f75bc3e03f8b2ad8400fd1f02cd

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

Frequently asked(5)

What is CVE-2026-72194?
CVE-2026-72194 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: add depth limit to indxfindbuffer to prevent stack overflow indxfindbuffer() recursively descends the B+ tree index with no depth limit. A crafted NTFS image with circular index node references causes unbounded recursion,…
When was CVE-2026-72194 disclosed?
CVE-2026-72194 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-72194 actively exploited?
CVE-2026-72194 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.0% of all scored CVEs.
What is the CVSS score of CVE-2026-72194?
CVE-2026-72194 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72194?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72194, 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-72194

Explore →

Is Your Infrastructure Affected by CVE-2026-72194?

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

Start Free Scan →Browse All CVEs