CVE-2026-64383

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 double-free in SMB2_flush() replay

SMB2_flush() keeps its response buffer bookkeeping across replay attempts. If a replayable flush response is received and the retry then fails before cifs_send_recv() stores a replacement response, flush_exit will free the stale response pointer a second time.

Reinitialize resp_buftype and rsp_iov at the top of the replay loop so cleanup only acts on response state produced by the current attempt. This fixes a double-free without changing replay handling for successful requests.

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 double-free in SMB2_flush() replay - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/878757163eea684750107a31ea134c103863515d
generic

smb: client: fix double-free in SMB2_flush() replay - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e27f40b682a5e42a2daae3ce6d96f0e0e16dedb
generic

smb: client: fix double-free in SMB2_flush() replay - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4be31c943a3a27a5a0251dbb8f5cb89059ec3d5a
generic

smb: client: fix double-free in SMB2_flush() replay - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3407240cde132a4b72d6429a2625a09a2f78adaf
generic

smb: client: fix double-free in SMB2_flush() replay - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/013a9a3da46c5dabcf18f65ea6a47874ba12a15d

Vendor Advisories for CVE-2026-64383(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.12—6.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 73× in last 7d / 354× 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 404 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-64383?
CVE-2026-64383 is a critical vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_flush() replay SMB2_flush() keeps its response buffer bookkeeping across replay attempts. If a replayable flush response is received and the retry then fails before cifssendrecv() stores a…
When was CVE-2026-64383 disclosed?
CVE-2026-64383 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-64383 actively exploited?
CVE-2026-64383 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-64383?
CVE-2026-64383 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-64383?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64383, 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-64383

Explore →

Is Your Infrastructure Affected by CVE-2026-64383?

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

Start Free Scan →Browse All CVEs