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.
Published: 2026-07-25
Score: 8.2 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Linux kernel’s smb server (ksmbd) writes the NTLMv2 session key before confirming that the client’s NTLMv2 response is valid. When authentication fails, the code still proceeds to exchange the key using KEY_XCH, allowing the client to carry a malformed proof, keep an invalid session key and receive a failure status, but still influence server state. This flaw effectively lets an attacker modify the session key during an attempted binding, potentially enabling unauthorized access or privilege escalation within the SMB session.

Affected Systems

All Linux kernel deployments that include the ksmbd component with SMB3 multichannel binding may be affected. No specific kernel version range is provided in the data, so any kernel build containing ksmbd that has not been updated to the fix is potentially vulnerable.

Risk and Exploitability

The flaw offers remote authentication bypass over SMB, with a CVSS score of 8.2. The EPSS score is below 1 %, indicating a very low current exploitation probability, and the issue is not yet present in the CISA KEV catalog. Nevertheless, because the vulnerability can be triggered over the network by any SMB client, its potential impact is high for systems that host untrusted SMB connections. Exploitability requires only SMB3 multichannel negotiation and the ability to send a binding session setup with a bad NT proof, making it an out‑of‑band network attack when the kernel is reachable.

Generated by OpenCVE AI on August 2, 2026 at 13:01 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the ksmbd authentication fix
  • Configure SMB3 settings to disable multichannel binding or set strict authentication requirements
  • Apply network filtering to limit SMB traffic to trusted hosts until a patch is applied

Generated by OpenCVE AI on August 2, 2026 at 13:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 01 Aug 2026 02:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-287

Thu, 30 Jul 2026 12:15:00 +0000


Mon, 27 Jul 2026 05:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H'}


Sun, 26 Jul 2026 02:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-287

Sat, 25 Jul 2026 09:30:00 +0000

Type Values Removed Values Added
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.
Title ksmbd: validate NTLMv2 response before updating session key
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-05T12:41:26.182Z

Reserved: 2026-07-19T15:36:31.785Z

Link: CVE-2026-64389

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-07-25T10:17:22.227

Modified: 2026-08-11T15:01:50.637

Link: CVE-2026-64389

cve-icon Redhat

Severity :

Publid Date: 2026-07-25T00:00:00Z

Links: CVE-2026-64389 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-02T13:15:03Z

Weaknesses
  • CWE-179

    Incorrect Behavior Order: Early Validation