CVE-2026-72205

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: 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:

ntfs: free volume-wide resources on fill_super failure

ntfs_fill_super()'s err_out_now path frees only the volume struct via kfree(vol), leaving several vol-owned allocations behind on every mount failure:

  • vol->nls_map, loaded by ntfs_init_fs_context() via
load_nls_default() (or replaced by an explicit nls= option in ntfs_parse_param()), is never unload_nls()'d.
  • vol->volume_label, allocated by load_system_files() through
ntfs_ucstonls() once the $Volume name attribute has been parsed, is not released by load_system_files()'s own error labels nor by the fill_super() inline cleanup that only runs on d_make_root() failure. Any later failure inside load_system_files() leaks it.
  • vol->lcn_empty_bits_per_page was kvfree()'d in
unl_upcase_iput_tmp_ino_err_out_now without clearing the pointer, so it could not be folded into a single common cleanup.

Because the failure paths never call ntfs_volume_free() and never reach the d_make_root() inline cleanup block (it sits above the label and is jumped over by the load_system_files() / kvmalloc failure gotos), these resources accumulate per failed mount attempt with no chance of recovery short of unloading the module. This is a silent leak: the inodes loaded prior to failure remain hashed but generic_shutdown_super() skips evict_inodes() when sb->s_root is unset, so no CHECK_DATA_CORRUPTION warning is emitted either.

Move the per-volume frees down to err_out_now and drop the lcn_empty_bits_per_page kvfree() from the upper label so the cleanup is performed exactly once on every failure path. Using unconditional kvfree() / kfree() / unload_nls() is safe because they all accept NULL and the upper labels that previously freed nls_map (the d_make_root() inline cleanup) already clear the pointer.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 18, 2026

References (2)

Vendor Advisories for CVE-2026-72205(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 22× in last 7d / 22× 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 08:37 UTCGHSA enrichment
  2. 2026-08-20 22:56 UTCEPSS rescore
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-18 13:49 UTCEPSS rescore
  5. 2026-08-18 13:49 UTCEPSS rescore
  6. 2026-08-18 07:25 UTCGHSA enrichment
  7. 2026-08-18 07:25 UTCNVD update
  8. 2026-08-18 07:03 UTCGHSA enrichment
  9. 2026-08-18 07:00 UTCMITRE cvelistV5
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 06:20 UTCGHSA enrichment
  12. 2026-08-17 06:18 UTCNVD update
  13. 2026-08-17 05:32 UTCEG score recompute
  14. 2026-08-17 05:32 UTCGHSA enrichment
  15. 2026-08-17 05:24 UTCMITRE cvelistV5
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:15 UTCEPSS rescore
  19. 2026-08-15 06:40 UTCGHSA enrichment
  20. 2026-08-15 06:23 UTCNVD update
  21. 2026-08-15 06:10 UTCEG score recompute
  22. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-72205?
CVE-2026-72205 is a publicly disclosed vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ntfs: free volume-wide resources on fill_super failure ntfsfillsuper()'s erroutnow path frees only the volume struct via kfree(vol), leaving several vol-owned allocations behind on every mount failure: vol->nlsmap, loaded by…
When was CVE-2026-72205 disclosed?
CVE-2026-72205 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72205 actively exploited?
CVE-2026-72205 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 90.0% of all scored CVEs.
How do I remediate CVE-2026-72205?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72205, 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-72205

Explore →

Is Your Infrastructure Affected by CVE-2026-72205?

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

Start Free Scan →Browse All CVEs