ksmbd: use memcmp() to compare ClientGUIDs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · < e8bb506e6ef749ac0336f3e579d8d02396b7d832| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: use memcmp() to compare ClientGUIDs
ClientGUID is a fixed-size binary value and can contain embedded NUL bytes. strncmp() stops comparing at the first NUL byte, so different ClientGUID values can incorrectly be treated as equal.
Use memcmp() in SMB3 multichannel session binding and FSCTL_VALIDATE_NEGOTIATE_INFO to compare all SMB2_CLIENT_GUID_SIZE bytes.
From the CVE record · Linux
The Linux kernel’s ksmbd component uses strncmp() to compare fixed-size ClientGUIDs, which can contain embedded NUL bytes. An SMB client supplying such values can cause different ClientGUIDs to be treated as equal during SMB3 multichannel session binding or FSCTL_VALIDATE_NEGOTIATE_INFO. Authentication requirements are not specified.
Anyone running Linux with ksmbd should check their kernel; affected versions are not specified.