CVE-2026-64598: Linux kernel · smb/client: Fix error code in smb2_aead_req_alloc()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in cad756733dc3985188983f3e2eb77e2927209099 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% 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 cannot 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 cad756733dc3985188983f3e2eb77e2927209099, aa37f5fef78dd11cbf983269da2031e12625c56d, a187883cc1dc784a4d32537f5d316f1b7b9ad76f +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Aug 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
|
| 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 error code in smb2_aead_req_alloc() The "*num_sgs" variable is a u32 so "ERR_PTR(*num_sgs)" doesn't work. We would have to do something similar to the previous line where it's cast to int and then long. However, it's simpler to store the return in an int ret variable. This bug would eventually result in a crash when dereference the invalid error pointer.
References
- git.kernel.org/stable/c/aa37f5fef78dd11cbf983269da2031e12625c56d (opens in a new tab)
- git.kernel.org/stable/c/cad756733dc3985188983f3e2eb77e2927209099 (opens in a new tab)
- git.kernel.org/stable/c/a187883cc1dc784a4d32537f5d316f1b7b9ad76f (opens in a new tab)
- git.kernel.org/stable/c/a1cc432cb0b0a1f74f98a0db3b94ca880c7947ac (opens in a new tab)
- git.kernel.org/stable/c/61f28012e5650c619223decdb7970e0d3162e949 (opens in a new tab)