CVE-2026-64356

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 25, 2026

Last Modified

September 4, 2026

Advisory Details (3)

Auto-updated Sep 4, 2026
No patch confirmed yet.
generic

xfs: fix memory leak in xfs_dqinode_metadir_create() - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfs: fix memory leak in xfs_dqinode_metadir_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/45de375b25060edf46e20abb36521ba530336ceb
generic

xfs: fix memory leak in xfs_dqinode_metadir_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06a2e6dbaa26c0740ac76dfa66b0aedc78d05820

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.

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 16× in last 7d / 57× 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.

Showing the most recent 100 of 105 total refreshes for this CVE.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 01:27 UTCEG score recompute
  3. 2026-09-20 01:27 UTCVendor advisory
  4. 2026-09-20 01:27 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 02:48 UTCEG score recompute
  7. 2026-09-18 02:48 UTCVendor advisory
  8. 2026-09-18 02:48 UTCGHSA enrichment
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-16 11:56 UTCEG score recompute
  11. 2026-09-16 11:56 UTCVendor advisory
  12. 2026-09-16 11:56 UTCGHSA enrichment
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-15 09:25 UTCEG score recompute
  15. 2026-09-15 09:25 UTCVendor advisory
  16. 2026-09-15 09:25 UTCGHSA enrichment
  17. 2026-09-13 21:32 UTCEG score recompute
  18. 2026-09-13 21:32 UTCVendor advisory
  19. 2026-09-13 21:32 UTCGHSA enrichment
  20. 2026-09-12 18:45 UTCVendor advisory
  21. 2026-09-12 18:45 UTCGHSA enrichment
  22. 2026-09-11 16:25 UTCEG score recompute
  23. 2026-09-11 16:25 UTCVendor advisory
  24. 2026-09-11 16:25 UTCGHSA enrichment
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 09:37 UTCEPSS rescore
  2. 2026-09-10 13:26 UTCEG score recompute
  3. 2026-09-10 13:26 UTCVendor advisory
  4. 2026-09-10 13:25 UTCGHSA enrichment
  5. 2026-09-09 08:37 UTCEG score recompute
  6. 2026-09-09 08:37 UTCVendor advisory
  7. 2026-09-09 08:37 UTCGHSA enrichment
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-07 21:17 UTCEG score recompute
  10. 2026-09-07 21:17 UTCVendor advisory
  11. 2026-09-07 21:17 UTCGHSA enrichment
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-05 19:20 UTCEG score recompute
  15. 2026-09-05 19:20 UTCGHSA enrichment
  16. 2026-09-05 15:31 UTCEPSS rescore
  17. 2026-09-04 16:02 UTCEG score recompute 5.50
  18. 2026-09-04 16:02 UTCGHSA enrichment
  19. 2026-09-04 16:02 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  20. 2026-09-04 12:41 UTCGHSA enrichment
  21. 2026-09-04 05:07 UTCEPSS rescore
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-08-30 20:02 UTCGHSA enrichment
  25. 2026-08-30 19:17 UTCEPSS rescore
  26. 2026-08-30 01:22 UTCEPSS rescore
  27. 2026-08-28 21:42 UTCEPSS rescore
  28. 2026-08-28 02:42 UTCGHSA enrichment
  29. 2026-08-26 14:47 UTCEPSS rescore
  30. 2026-08-25 13:49 UTCEPSS rescore
  31. 2026-08-25 09:21 UTCGHSA enrichment
  32. 2026-08-22 16:01 UTCGHSA enrichment
  33. 2026-08-21 23:49 UTCEPSS rescore
  34. 2026-08-20 22:55 UTCEPSS rescore
  35. 2026-08-19 22:40 UTCGHSA enrichment
  36. 2026-08-19 17:04 UTCEPSS rescore
  37. 2026-08-18 13:48 UTCEPSS rescore
  38. 2026-08-17 13:47 UTCEPSS rescore
  39. 2026-08-17 05:25 UTCNVD update
  40. 2026-08-17 05:19 UTCGHSA enrichment
  41. 2026-08-17 05:05 UTCMITRE cvelistV5
  42. 2026-08-17 01:49 UTCGHSA enrichment
  43. 2026-08-16 14:56 UTCEPSS rescore
  44. 2026-08-15 01:30 UTCEPSS rescore
  45. 2026-08-14 08:28 UTCGHSA enrichment
  46. 2026-08-13 22:00 UTCEPSS rescore
  47. 2026-08-12 13:51 UTCEPSS rescore
  48. 2026-08-11 15:07 UTCGHSA enrichment
  49. 2026-08-11 10:55 UTCGHSA enrichment
  50. 2026-08-11 00:00 UTCEPSS rescore
  51. 2026-08-09 13:47 UTCEPSS rescore
  52. 2026-08-08 17:35 UTCGHSA enrichment
  53. 2026-08-08 16:37 UTCEPSS rescore
  54. 2026-08-06 13:47 UTCEPSS rescore
  55. 2026-08-06 00:14 UTCGHSA enrichment
  56. 2026-08-05 19:17 UTCEPSS rescore
  57. 2026-08-05 19:17 UTCEPSS rescore
  58. 2026-08-04 15:10 UTCEPSS rescore
  59. 2026-08-04 10:39 UTCEPSS rescore
  60. 2026-08-03 10:36 UTCEPSS rescore
  61. 2026-08-03 06:54 UTCGHSA enrichment
  62. 2026-08-02 02:27 UTCEPSS rescore
  63. 2026-07-31 13:33 UTCEG score recompute
  64. 2026-07-31 13:33 UTCGHSA enrichment
  65. 2026-07-30 16:28 UTCEPSS rescore
  66. 2026-07-30 01:30 UTCEPSS rescore
  67. 2026-07-30 01:30 UTCEPSS rescore
  68. 2026-07-28 20:12 UTCEG score recompute
  69. 2026-07-28 20:12 UTCGHSA enrichment
  70. 2026-07-28 15:37 UTCEPSS rescore
  71. 2026-07-27 14:14 UTCEPSS rescore
  72. 2026-07-26 14:54 UTCEPSS rescore
  73. 2026-07-26 14:54 UTCEPSS rescore
  74. 2026-07-26 02:49 UTCEG score recompute
  75. 2026-07-26 02:49 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-64356?
CVE-2026-64356 is a medium 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 September 4, 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 96.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64356?
CVE-2026-64356 has a CVSS v3 base score of 5.5 (NVD).
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.