CVE-2026-64387

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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: 0%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:

smb: client: fix query directory replay double-free

A response-bearing attempt can return a replayable error and free its response buffer. If SMB2_query_directory_init() fails before the next send, cleanup retains the previous buffer type and frees that response again.

Reset response bookkeeping before each attempt to prevent the stale free.

CVSS v3
9.8
EG Score
9.8(medium)
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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (5)

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

smb: client: fix query directory replay double-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9647492b5e41954be59d5157eddbcd4cdc1656f7
generic

smb: client: fix query directory replay double-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3409aedf3c81a810243da94164f6621c9d205c98
generic

smb: client: fix query directory replay double-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3317a5d015fca976475aa71df224056777316fde
generic

smb: client: fix query directory replay double-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1665f25b1dea30bf2d02e16245d203a944c9d994
generic

smb: client: fix query directory replay double-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00b0fa425941438b664950a8ee65dfba2def4336

Vendor Advisories for CVE-2026-64387(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
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 70× in last 7d / 346× 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 394 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64387?
CVE-2026-64387 is a critical vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: smb: client: fix query directory replay double-free A response-bearing attempt can return a replayable error and free its response buffer. If SMB2querydirectory_init() fails before the next send, cleanup retains the previous buffer…
When was CVE-2026-64387 disclosed?
CVE-2026-64387 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-64387 actively exploited?
CVE-2026-64387 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 62.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64387?
CVE-2026-64387 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-64387?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64387, 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-64387

Explore →

Is Your Infrastructure Affected by CVE-2026-64387?

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