ksmbd: fix potencial OOB in get_file_all_info() for compound requests
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d · < 9d7032851d6f5adbe2739601ca456c0ad3b422f0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix potencial OOB in get_file_all_info() for compound requests
When a compound request consists of QUERY_DIRECTORY + QUERY_INFO (FILE_ALL_INFORMATION) and the first command consumes nearly the entire max_trans_size, get_file_all_info() would blindly call smbConvertToUTF16() with PATH_MAX, causing out-of-bounds write beyond the response buffer. In get_file_all_info(), there was a missing validation check for the client-provided OutputBufferLength before copying the filename into FileName field of the smb2_file_all_info structure. If the filename length exceeds the available buffer space, it could lead to potential buffer overflows or memory corruption during smbConvertToUTF16 conversion. This calculating the actual free buffer size using smb2_calc_max_out_buf_len() and returning -EINVAL if the buffer is insufficient and updating smbConvertToUTF16 to use the actual filename length (clamped by PATH_MAX) to ensure a safe copy operation.
From the CVE record · Linux
The Linux kernel's ksmbd handler for FILE_ALL_INFORMATION did not check the client-provided output buffer length before copying a filename. A crafted compound QUERY_DIRECTORY and QUERY_INFO request could cause an out-of-bounds write and memory corruption when the first command uses nearly all of max_trans_size. The input does not specify authentication requirements or user interaction.
Engineers running Linux kernels with ksmbd should check whether their kernel includes this fix; affected versions are not specified.