smb/client: fix out-of-bounds read in symlink_data()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 76894f3e2f71177747b8b4763fb180e800279585 · < d62b8d236fab503c6fec1d3e9a38bea71feaca20| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
smb/client: fix out-of-bounds read in symlink_data()
Since smb2_check_message() returns success without length validation for the symlink error response, in symlink_data() it is possible for iov->iov_len to be smaller than sizeof(struct smb2_err_rsp). If the buffer only contains the base SMB2 header (64 bytes), accessing err->ErrorContextCount (at offset 66) or err->ByteCount later in symlink_data() will cause an out-of-bounds read.
From the CVE record · Linux
The Linux kernel SMB client does not validate the length of a symlink error response before symlink_data() reads fields from it. A response containing only the 64-byte SMB2 header can cause an out-of-bounds read. The input does not specify authentication or user-interaction requirements.
Teams running Linux kernels with the SMB client should check their systems; affected versions are not specified.