CVE-2026-64389 json
ksmbd: validate NTLMv2 response before updating session key
published 2026-07-25 3 mo ago modified 2026-10-30 10 d ago also EUVD-2026-48933
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.114, 6.18.40, 7.1.4, 7.2
- linux Debian 13 6.12.115-2
- linux Debian 14 7.1.4-1
debian advisories DEBIAN-CVE-2026-64389
- linux Ubuntu 26.04 LTS 7.0.0-31.31
- linux-aws Ubuntu 26.04 LTS 7.0.0-1012.12
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1011.11
- linux-gke Ubuntu 26.04 LTS 7.0.0-1006.7
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1013.13
- linux-azure Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-raspi Ubuntu 26.04 LTS 7.0.0-1019.19
- linux-riscv Ubuntu 26.04 LTS 7.0.0-31.31.1
ubuntu advisories UBUNTU-CVE-2026-64389
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.1.7-1.1
opensuse advisories openSUSE-SU-2026:11476-1
- git.kernel.org/stable/c/e589e997bddde0a6f45672dd871cba7b3ff28e17 commit
- git.kernel.org/stable/c/a6a951416b55eaf51ea2742f7ba786f240e70137 commit
- git.kernel.org/stable/c/f5d74c186bab26a5d5a025305e67edd0888aa34d commit
- git.kernel.org/stable/c/b56400364aed5c34d6e1a0b493081290a5328a9c commit
- git.kernel.org/stable/c/89ca7756d5566ba636bb9092cdbe57dab095e136 commit
- git.kernel.org/stable/c/954d196bebb2b50151cb96454c72dc113b2af1ac commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-64389 updated
kernel: ksmbd: validate NTLMv2 response before updating session key
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/e589e997bddde0a6f45672dd871cba7b3ff28e17
- git.kernel.org /stable/c/a6a951416b55eaf51ea2742f7ba786f240e70137
- git.kernel.org /stable/c/f5d74c186bab26a5d5a025305e67edd0888aa34d
-
git.kernel.org
/stable/c/b56400364aed5c34d6e1a0b493081290a5328a9c
patch
-
git.kernel.org
/stable/c/89ca7756d5566ba636bb9092cdbe57dab095e136
patch
-
git.kernel.org
/stable/c/954d196bebb2b50151cb96454c72dc113b2af1ac
patch
Sources
- CVE List CVE-2026-64389
- NVD CVE-2026-64389
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.