CVE-2026-64356

UNRATEDCVSS · not yet scored
—
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:

xfs: fix memory leak in xfs_dqinode_metadir_create()

If xfs_metadir_create() fails in xfs_dqinode_metadir_create(), the current code returns directly, leaking the allocated update and transaction state. If the subsequent commit fails, the caller-owned inode reference is left behind.

Fix this memory leak by routing the create failure path through xfs_metadir_cancel(). For both create and commit failures, finish and release any inode returned to the caller, mirroring the unwind pattern in xfs_metadir_mkdir().

The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1.1.

An x86_64 allyesconfig build showed no new warnings. Runtime validation used kprobe fault injection during mount -o uquota on a metadir XFS image. Injecting xfs_metadir_create() reproduced the old active-update path that left mount stuck later in mount setup; after this change, the same injection reported cancel_hits=1 and irele_hits=1. Injecting xfs_metadir_commit() exercised the old inode-reference leak path; after this change, it reported irele_hits=1.

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
7%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

References (3)

Vendor Advisories for CVE-2026-64356(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Data Freshness Timeline

(refreshed 6× in last 7d / 39× 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 01:22 UTCEPSS rescore
  2. 2026-08-28 21:42 UTCEPSS rescore
  3. 2026-08-28 02:42 UTCGHSA enrichment
  4. 2026-08-26 14:47 UTCEPSS rescore
  5. 2026-08-25 13:49 UTCEPSS rescore
  6. 2026-08-25 09:21 UTCGHSA enrichment
  7. 2026-08-22 16:01 UTCGHSA enrichment
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 22:40 UTCGHSA enrichment
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 05:25 UTCNVD update
  15. 2026-08-17 05:19 UTCGHSA enrichment
  16. 2026-08-17 05:05 UTCMITRE cvelistV5
  17. 2026-08-17 01:49 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 08:28 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 15:07 UTCGHSA enrichment
  24. 2026-08-11 10:55 UTCGHSA enrichment
  25. 2026-08-11 00:00 UTCEPSS rescore
Show 30 more
  1. 2026-08-09 13:47 UTCEPSS rescore
  2. 2026-08-08 17:35 UTCGHSA enrichment
  3. 2026-08-08 16:37 UTCEPSS rescore
  4. 2026-08-06 13:47 UTCEPSS rescore
  5. 2026-08-06 00:14 UTCGHSA enrichment
  6. 2026-08-05 19:17 UTCEPSS rescore
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-04 15:10 UTCEPSS rescore
  9. 2026-08-04 10:39 UTCEPSS rescore
  10. 2026-08-03 10:36 UTCEPSS rescore
  11. 2026-08-03 06:54 UTCGHSA enrichment
  12. 2026-08-02 02:27 UTCEPSS rescore
  13. 2026-07-31 13:33 UTCEG score recompute
  14. 2026-07-31 13:33 UTCGHSA enrichment
  15. 2026-07-30 16:28 UTCEPSS rescore
  16. 2026-07-30 01:30 UTCEPSS rescore
  17. 2026-07-30 01:30 UTCEPSS rescore
  18. 2026-07-28 20:12 UTCEG score recompute
  19. 2026-07-28 20:12 UTCGHSA enrichment
  20. 2026-07-28 15:37 UTCEPSS rescore
  21. 2026-07-27 14:14 UTCEPSS rescore
  22. 2026-07-26 14:54 UTCEPSS rescore
  23. 2026-07-26 14:54 UTCEPSS rescore
  24. 2026-07-26 02:49 UTCEG score recompute
  25. 2026-07-26 02:49 UTCGHSA enrichment
  26. 2026-07-25 14:18 UTCEPSS rescore
  27. 2026-07-25 14:18 UTCEPSS rescore
  28. 2026-07-25 10:39 UTCNVD update
  29. 2026-07-25 09:37 UTCEG score recompute
  30. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64356?
CVE-2026-64356 is a publicly disclosed vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: xfs: fix memory leak in xfsdqinodemetadir_create() If xfsmetadircreate() fails in xfsdqinodemetadir_create(), the current code returns directly, leaking the allocated update and transaction state. If the subsequent commit fails,…
When was CVE-2026-64356 disclosed?
CVE-2026-64356 was first published in the National Vulnerability Database on July 25, 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-64356 actively exploited?
CVE-2026-64356 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 92.5% of all scored CVEs.
How do I remediate CVE-2026-64356?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64356, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64356

Explore →

Is Your Infrastructure Affected by CVE-2026-64356?

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

Start Free Scan →Browse All CVEs