ksmbd: defer destroy_previous_session() until after NTLM authentication
- 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
- 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: defer destroy_previous_session() until after NTLM authentication In ntlm_authenticate(), destroy_previous_session() is called using a user pointer resolved from the client-supplied NTLM blob username field before the NTLMv2 response is validated. An authenticated attacker can set the NTLM blob username to match a victim account and set PreviousSessionId to the victim's session ID; destroy_previous_session() destroys the victim's session while ksmbd_decode_ntlmssp_auth_blob() subsequently rejects the request with -EPERM. Move destroy_previous_session() and the prev_id assignment to after ksmbd_decode_ntlmssp_auth_blob() returns success and use sess->user rather than the pre-authentication lookup result. This matches the ordering already used by krb5_authenticate(), where destroy_previous_session() is called only after ksmbd_krb5_authenticate() returns success.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.15
References 7
git.kernel.org
- stable/c/ab0230257ebdf48b07eaa679a8c92bc842fe3498
- stable/c/370b0ec8822b69c9073265e16b7daaa8201c9a4f
- stable/c/5c833074b549e5db125436a6f681af682261f785
- stable/c/243f1614ef2aca2d62a744575f1c24b07cd42757
- stable/c/18705cace0619fd2123737dcd028147774f38181
- stable/c/0ff12308c8a6c16ab68f0a487ffa93d69001dc18
- stable/c/c74801ee524f477c174a1899782b6c3b6918d407