ksmbd: use memcmp() to compare ClientGUIDs
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.189, 6.6.158, 6.12.111, 6.18.53, 7.1.8
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · fixed in 7bde6f181fa307d2cc1ec2b0313ac8e9811c8232; From e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · fixed in 5a0367bf5ce420be7b19936def2e90adcf32a683; From e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · fixed in ba2a5b66f1d414eb8403d655f8813783892cfc85; From e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · fixed in a386c83043015a703e227775f778e40343f45911; From e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · fixed in d535363299822c5caa543787b21bd5cfa3e41949; From e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · fixed in e8bb506e6ef749ac0336f3e579d8d02396b7d832
- Linux Linux
5.15
- KernelLinux
From 5.15.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.1.8