Linux ksmbd data exposure in POSIX filesystem information responses
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · < ab057f271ef60ff8163818badc3de75c480eca07| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION
smb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION, that is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns FileSysIdentifier. Those eight 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.
Report the file system id statfs() returned, which is what the field is for. FileSysIdentifier is __le64 and f_fsid is a pair of ints, so assemble the value first, val[0] as the low half, and convert it on the way out.
From the CVE record · Linux
The Linux kernel’s ksmbd can return uninitialized response-buffer contents in the FileSysIdentifier field of FS_POSIX_INFORMATION. An SMB client can receive data from an earlier reply when a compound request causes that reply to be replaced by a short error response; a standalone request does not leak data. The input does not specify whether authentication is required.
Anyone running the Linux kernel with ksmbd should check whether their kernel is affected; affected versions are not specified.