Linux ksmbd data exposure in filesystem control information responses
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · < 03bb4338c3a7c3fc4decf699a35753f0891aab2a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION
smb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION, that is the whole of struct smb2_fs_control_info, but never assigns FileSystemControlFlags. Those four bytes go to the client as they are found in the response buffer.
The buffer is zeroed on allocation, so a standalone request leaks nothing. A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.
ksmbd does not implement quota tracking, so report no control flags.
From the CVE record · Linux
The Linux kernel's ksmbd leaves four bytes of FileSystemControlFlags uninitialized in an FS_CONTROL_INFORMATION response. A network client can receive bytes left in the response buffer by a preceding reply through a compound SMB request; a standalone request does not leak data. Authentication requirements and user interaction are not specified.
Engineers running Linux kernels with ksmbd should check their systems; affected versions are not specified.