In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate NTLMv2 response before updating session key ksmbd_auth_ntlmv2()… (CVE-2026-64389)
A vulnerability in the Linux kernel's ksmbd component allowed the NTLMv2 session key to be updated before the NTLMv2 response was properly validated. This flaw could let an attacker modify the session key during an authentication failure when using SMB3 multichannel binding, potentially impacting session integrity. The issue was fixed by changing the code to only update the session key after successful authentication verification.
AI Analysis
Technical Summary
The Linux kernel's ksmbd_auth_ntlmv2() function previously derived the NTLMv2 session key into sess->sess_key before verifying the NTLMv2 response. If authentication failed, ksmbd_decode_ntlmssp_auth_blob() still proceeded to the KEY_XCH phase, allowing modification of sess->sess_key despite the failure. With SMB3 multichannel binding, this flaw allowed a client to send a binding session setup with an invalid NT proof and still alter the session key before a STATUS_LOGON_FAILURE was returned. The fix involves deriving the session key into a local buffer and only copying it to sess->sess_key after successful proof validation, ensuring KEY_XCH processing occurs only after authentication succeeds.
Potential Impact
An attacker could potentially manipulate the session key during a failed authentication attempt in SMB3 multichannel binding scenarios, which may affect session integrity and security. No known exploits in the wild have been reported. The vulnerability could lead to unauthorized session key modification before authentication failure is enforced.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by validating the NTLMv2 response before updating the session key. Users should apply the official kernel updates that include this patch. Since this is not a cloud service, remediation requires updating affected Linux kernel versions once the patch is available. Patch status is not yet confirmed in the provided data; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate NTLMv2 response before updating session key ksmbd_auth_ntlmv2()… (CVE-2026-64389)
Description
A vulnerability in the Linux kernel's ksmbd component allowed the NTLMv2 session key to be updated before the NTLMv2 response was properly validated. This flaw could let an attacker modify the session key during an authentication failure when using SMB3 multichannel binding, potentially impacting session integrity. The issue was fixed by changing the code to only update the session key after successful authentication verification.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's ksmbd_auth_ntlmv2() function previously derived the NTLMv2 session key into sess->sess_key before verifying the NTLMv2 response. If authentication failed, ksmbd_decode_ntlmssp_auth_blob() still proceeded to the KEY_XCH phase, allowing modification of sess->sess_key despite the failure. With SMB3 multichannel binding, this flaw allowed a client to send a binding session setup with an invalid NT proof and still alter the session key before a STATUS_LOGON_FAILURE was returned. The fix involves deriving the session key into a local buffer and only copying it to sess->sess_key after successful proof validation, ensuring KEY_XCH processing occurs only after authentication succeeds.
Potential Impact
An attacker could potentially manipulate the session key during a failed authentication attempt in SMB3 multichannel binding scenarios, which may affect session integrity and security. No known exploits in the wild have been reported. The vulnerability could lead to unauthorized session key modification before authentication failure is enforced.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by validating the NTLMv2 response before updating the session key. Users should apply the official kernel updates that include this patch. Since this is not a cloud service, remediation requires updating affected Linux kernel versions once the patch is available. Patch status is not yet confirmed in the provided data; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-fxvf-vm38-6pxw
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64389"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420b9c2644c7f8084755
Added to database: 07/25/2026, 23:08:59 UTC
Last enriched: 07/25/2026, 23:28:45 UTC
Last updated: 07/26/2026, 03:58:19 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.