CVE-2026-64381: Linux kernel · smb: client: Fix next buffer leak in receive_encrypted_standard()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 67097772df7791c53d608f04bd31c676ccf79b83 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:04 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in 67097772df7791c53d608f04bd31c676ccf79b83, 297243e365fc9fe2f8e9b7dd535a65d922cd108b, 9136a08dc29328edd9867f2545e73906ac9df93b +5
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 6 Nov 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
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | 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 next buffer leak in receive_encrypted_standard() receive_encrypted_standard() allocates next_buffer before checking whether the number of compound PDUs already reached MAX_COMPOUND. If the limit check fails, the function returns immediately and the newly allocated next_buffer is not assigned to server->smallbuf/server->bigbuf, making it leaked. Move the MAX_COMPOUND check before allocating next_buffer.
References
- git.kernel.org/stable/c/94e4f672db029414b9888b5137a7559f1febf2d8 (opens in a new tab)
- git.kernel.org/stable/c/68fc0b6cc03ca58060c0f36454e169f5fe258974 (opens in a new tab)
- git.kernel.org/stable/c/07e0ab81df1790afa35732a4e8e07ff831b29008 (opens in a new tab)
- git.kernel.org/stable/c/9136a08dc29328edd9867f2545e73906ac9df93b (opens in a new tab)
- git.kernel.org/stable/c/67097772df7791c53d608f04bd31c676ccf79b83 (opens in a new tab)
- git.kernel.org/stable/c/297243e365fc9fe2f8e9b7dd535a65d922cd108b (opens in a new tab)
- git.kernel.org/stable/c/927d4805aea0a287d36dd4f826ee24d69a2afee3 (opens in a new tab)
- git.kernel.org/stable/c/1c6267a1d5cf4c73b656f8181b310cbbb3e4767b (opens in a new tab)