CVE-2026-68130

ksmbd: defer destroy_previous_session() until after NTLM authentication

N/A
Published: August 10, 2026 at 11:58 AM UTC
Updated: August 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.15 ≤ v < 5.15.2175.15 ≤ v < 6.1.1835.15 ≤ v < 6.12.1015.15 ≤ v < 6.18.425.15 ≤ v < 6.6.1485.15 ≤ v < 7.1.65.15 ≤ v < 7.25.15e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9
Vendor states this is fixed in 0ff12308c8a6c16ab68f0a487ffa93d69001dc18 (fixed)
Vendor states this is fixed in 18705cace0619fd2123737dcd028147774f38181 (fixed)
Vendor states this is fixed in 243f1614ef2aca2d62a744575f1c24b07cd42757 (fixed)
Vendor states this is fixed in 370b0ec8822b69c9073265e16b7daaa8201c9a4f (fixed)
Vendor states this is fixed in 5c833074b549e5db125436a6f681af682261f785 (fixed)
Vendor states this is fixed in ab0230257ebdf48b07eaa679a8c92bc842fe3498 (fixed)
Vendor states this is fixed in c74801ee524f477c174a1899782b6c3b6918d407 (fixed)
Vendor states this is fixed in 5.15 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card