CVE-2026-64387: Linux kernel · smb: client: fix query directory replay double-free
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in 9647492b5e41954be59d5157eddbcd4cdc1656f7 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in 9647492b5e41954be59d5157eddbcd4cdc1656f7, 3409aedf3c81a810243da94164f6621c9d205c98, 3317a5d015fca976475aa71df224056777316fde +3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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.
References
- git.kernel.org/stable/c/3409aedf3c81a810243da94164f6621c9d205c98 (opens in a new tab)
- git.kernel.org/stable/c/1665f25b1dea30bf2d02e16245d203a944c9d994 (opens in a new tab)
- git.kernel.org/stable/c/00b0fa425941438b664950a8ee65dfba2def4336 (opens in a new tab)
- git.kernel.org/stable/c/3317a5d015fca976475aa71df224056777316fde (opens in a new tab)
- git.kernel.org/stable/c/9647492b5e41954be59d5157eddbcd4cdc1656f7 (opens in a new tab)