CVE-2026-99385
Severity unknownNo known exploitationFix availablesmb: client: fix buffer overflow in SMB2_tcon()
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 16% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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]
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 62a1a439e0fdd4ec8a80dc00fcbb9f26b5c34de1 before acf25a7be39dccdbf60fdf3d437dd7832fa4b6d3 | acf25a7be39dccdbf60fdf3d437dd7832fa4b6d3 | CVE Program |
| Linux | Linux | from 62a1a439e0fdd4ec8a80dc00fcbb9f26b5c34de1 before d26f7fbca42532c6c79efdceb4bd5198e1849314 | d26f7fbca42532c6c79efdceb4bd5198e1849314 | CVE Program |
| Linux | Linux | from 62a1a439e0fdd4ec8a80dc00fcbb9f26b5c34de1 before 73cc469b0ff7551f8537ea919709973e6dc4f514 | 73cc469b0ff7551f8537ea919709973e6dc4f514 | CVE Program |
| Linux | Linux | from 62a1a439e0fdd4ec8a80dc00fcbb9f26b5c34de1 before 75fd4c72aa3dcfabb318144636f416be6796d423 | 75fd4c72aa3dcfabb318144636f416be6796d423 | CVE Program |
| Linux | Linux | 3.8 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.117 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.61 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.2 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 3.8 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/73cc469b0ff7551f8537ea919709973e6dc4f514 (opens in a new tab)
- https://git.kernel.org/stable/c/75fd4c72aa3dcfabb318144636f416be6796d423 (opens in a new tab)
- https://git.kernel.org/stable/c/acf25a7be39dccdbf60fdf3d437dd7832fa4b6d3 (opens in a new tab)
- https://git.kernel.org/stable/c/d26f7fbca42532c6c79efdceb4bd5198e1849314 (opens in a new tab)