smb: client: reject a tree connect response whose byte count is too small
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ cc20c031bb067eb3280a1c4b5c42295093e24863 · < 65deb18359341141d37dc86fc7853511be3c87a7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
smb: client: reject a tree connect response whose byte count is too small
CIFSTCon() bounds its strnlen() over the byte area with the server's ByteCount minus two, which for ByteCount 0 or 1 goes negative as an int and converts to a huge size_t. The later subtraction wraps the __u16 bytes_left, and that is what bounds cifs_strndup_from_utf16(): a bound of up to 65535 against a ~16 KB cifs_req_poolp object runs off the end of the slab object, and the bytes reach userspace through tcon->nativeFileSystem in /proc/fs/cifs/DebugData.
Reject a byte area too small for what the parser consumes. Two bytes is the least it can consume, and no conformant response carries fewer. The new trace point is the 129th smb_eio_trace entry, which __mode(byte) cannot represent, so the attribute goes with it.
From the CVE record · Linux
The Linux kernel SMB client mishandles a tree connect response with a ByteCount of 0 or 1, allowing a read beyond a slab object. When an SMB server sends such a response, the client can expose the read bytes to userspace through /proc/fs/cifs/DebugData.
Engineers running Linux kernels with the SMB client should check whether their kernel includes the fix; affected versions were not specified.