CVE-2026-99385: Linux kernel · smb: client: fix buffer overflow in SMB2_tcon()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d26f7fbca42532c6c79efdceb4bd5198e1849314 : update Linux kernel when convenient.
Data as of 19 Nov 2026, 14:34 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in d26f7fbca42532c6c79efdceb4bd5198e1849314, acf25a7be39dccdbf60fdf3d437dd7832fa4b6d3, 75fd4c72aa3dcfabb318144636f416be6796d423 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 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 18 Nov 2026.
What to do
Upgrade Linux kernel to d26f7fbca42532c6c79efdceb4bd5198e1849314, acf25a7be39dccdbf60fdf3d437dd7832fa4b6d3, 75fd4c72aa3dcfabb318144636f416be6796d423 or 73cc469b0ff7551f8537ea919709973e6dc4f514.
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– |
Description
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix buffer overflow in SMB2_tcon() In SMB2_tcon(), unc_path is allocated with a fixed buffer size of MAX_SHARENAME_LENGTH * 2 bytes (672 bytes). However, the user-controlled UNC path (tree) length is passed to cifs_strtoUTF16(), which assumes the destination buffer is large enough and writes strlen(tree) + 1 UTF-16 code units. Commit 62a1a439e0fd ("cifs: clean up handling of unc= option") removed the length check on UNC mount options, allowing mount paths to exceed MAX_SHARENAME_LENGTH while retaining the fixed-size buffer allocation in SMB2_tcon(). Consequently, an oversized UNC string causes cifs_strtoUTF16() to write past the end of the heap object, resulting in a slab-out-of-bounds write. Furthermore, if a tree exceeds MAX_TREE_SIZE characters, strscpy() truncates it in cifs_tcon::tree_name, causing subsequent reconnects or failovers to fail. Fix this by first verifying that the length of tree does not exceed MAX_TREE_SIZE, returning -EINVAL if it does. Then, dynamically allocate unc_path based on the length of tree so that it safely accommodates all UTF-16 code units for paths within MAX_TREE_SIZE. [pc: remove unused MAX_SHARENAME_LENGTH]
References
- git.kernel.org/stable/c/75fd4c72aa3dcfabb318144636f416be6796d423 (opens in a new tab)
- git.kernel.org/stable/c/acf25a7be39dccdbf60fdf3d437dd7832fa4b6d3 (opens in a new tab)
- git.kernel.org/stable/c/d26f7fbca42532c6c79efdceb4bd5198e1849314 (opens in a new tab)
- git.kernel.org/stable/c/73cc469b0ff7551f8537ea919709973e6dc4f514 (opens in a new tab)