CVE-2026-64389ksmbd: validate NTLMv2 response before updating session key
- 8.2HighCVSS base score
- 0.48%Exploitation in 30 daysEPSS · top 58% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate NTLMv2 response before updating session key ksmbd_auth_ntlmv2() derives the NTLMv2 session key into sess->sess_key before it verifies the NTLMv2 response. ksmbd_decode_ntlmssp_auth_blob() then continues into KEY_XCH even when ksmbd_auth_ntlmv2() failed. With SMB3 multichannel binding, the failed authentication operates on an existing session and the session setup error path does not expire binding sessions. A client can send a binding session setup with a bad NT proof and KEY_XCH and still modify sess->sess_key before STATUS_LOGON_FAILURE is returned. Relevant path: smb2_sess_setup() -> conn->binding = true -> ntlm_authenticate() -> session_user() -> ksmbd_decode_ntlmssp_auth_blob() -> ksmbd_auth_ntlmv2() -> calc_ntlmv2_hash() -> hmac_md5_usingrawkey(..., sess->sess_key) -> crypto_memneq() returns mismatch -> KEY_XCH arc4_crypt(..., sess->sess_key, ...) -> out_err without expiring the binding session Derive the base session key into a local buffer and copy it to sess->sess_key only after the proof matches. Return immediately on authentication failure so KEY_XCH is only processed after successful authentication.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
| NVDNVD · Modified | 3.1 | High8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
- EPSS (exploitation in 30 days)
- 0.48% · top 58% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.
Affected products
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < e589e997bddde0a6f45672dd871cba7b3ff28e17
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < a6a951416b55eaf51ea2742f7ba786f240e70137
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < f5d74c186bab26a5d5a025305e67edd0888aa34d
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < b56400364aed5c34d6e1a0b493081290a5328a9c
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 89ca7756d5566ba636bb9092cdbe57dab095e136
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 954d196bebb2b50151cb96454c72dc113b2af1ac
- affected 5.15
- unaffected < 5.15
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.4 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/e589e997bddde0a6f45672dd871cba7b3ff28e17 (opens in a new tab)
- https://git.kernel.org/stable/c/a6a951416b55eaf51ea2742f7ba786f240e70137 (opens in a new tab)
- https://git.kernel.org/stable/c/f5d74c186bab26a5d5a025305e67edd0888aa34d (opens in a new tab)
- https://git.kernel.org/stable/c/b56400364aed5c34d6e1a0b493081290a5328a9c (opens in a new tab)
- https://git.kernel.org/stable/c/89ca7756d5566ba636bb9092cdbe57dab095e136 (opens in a new tab)
- https://git.kernel.org/stable/c/954d196bebb2b50151cb96454c72dc113b2af1ac (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-48933 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64389)Record last updated .