smb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f5778c398713692a16150ae96e5c8270bab8399f · < 078fae8f50adebb903ccf2252b44391324571e78| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path
smb2_ioctl_query_info() has two response-copy branches: PASSTHRU_FSCTL and the default QUERY_INFO path. The QUERY_INFO branch clamps qi.input_buffer_length to the server-reported OutputBufferLength and then copies qi.input_buffer_length bytes from qi_rsp->Buffer to userspace, but it never verifies that the flexible-array payload actually fits within rsp_iov[1].iov_len.
A malicious server can return OutputBufferLength larger than the actual QUERY_INFO response, causing copy_to_user() to walk past the response buffer and expose adjacent kernel heap to userspace.
Guard the QUERY_INFO copy with a bounds check on the actual Buffer payload. Use struct_size(qi_rsp, Buffer, qi.input_buffer_length) rather than an open-coded addition so the guard cannot overflow on 32-bit builds.
From the CVE record · Linux
The Linux kernel SMB client's QUERY_INFO response path can read beyond its response buffer because it does not check that the reported output fits the received payload. A malicious SMB server can trigger the out-of-bounds read and expose adjacent kernel heap data to userspace when a client processes its response; no authentication or user-interaction requirements are specified.
Engineers running Linux kernels that use the SMB client should check whether their kernel includes the QUERY_INFO bounds-check fix; affected versions are not specified.