CVE-2026-53383Linux Linux Kernel NULL Pointer Dereference
NVDCVSS scored by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Vulnerability Summary
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: reject non-VALID session in compound request branch
smb2_check_user_session() takes a shortcut for any operation that is not
the first in a COMPOUND request: it reuses work->sess (the session bound by
the first operation) and validates only the SessionId, then returns
"valid". It never re-checks work->sess->state == SMB2_SESSION_VALID, and a
SessionId of 0xFFFFFFFFFFFFFFFF (ULLONG_MAX, the MS-SMB2 related-operation
value) skips even the id comparison. The standalone path
(ksmbd_session_lookup_all() plus the SESSION_SETUP state machine) does
enforce the VALID state; the compound branch bypasses all of it.
A SESSION_SETUP carrying only an NTLM Type-1 (NtLmNegotiate) blob publishes
a fresh SMB2_SESSION_IN_PROGRESS session whose sess->user is still NULL
(->user is assigned later, by ntlm_authenticate()). Used as operation 1 of
a COMPOUND with operation 2 = TREE_CONNECT (related, SessionId=ULLONG_MAX,
\\host\IPC$), the tree-connect then runs on that IN_PROGRESS session and
reaches ksmbd_ipc_tree_connect_request(), which dereferences
user_name(sess->user) with sess->user == NULL (transport_ipc.c:687/701/704)
-> remote NULL-pointer dereference and a kernel Oops that wedges the ksmbd
worker for all clients.
Reject any non-first compound operation that lands on a session which is
not SMB2_SESSION_VALID, mirroring the validity the standalone lookup path
enforces. SESSION_SETUP itself legitimately runs on an IN_PROGRESS session,
but it is never carried as a non-first compound operation, so multi-leg
authentication is unaffected by this check.
ksmbd: reject non-VALID session in compound request branch
smb2_check_user_session() takes a shortcut for any operation that is not
the first in a COMPOUND request: it reuses work->sess (the session bound by
the first operation) and validates only the SessionId, then returns
"valid". It never re-checks work->sess->state == SMB2_SESSION_VALID, and a
SessionId of 0xFFFFFFFFFFFFFFFF (ULLONG_MAX, the MS-SMB2 related-operation
value) skips even the id comparison. The standalone path
(ksmbd_session_lookup_all() plus the SESSION_SETUP state machine) does
enforce the VALID state; the compound branch bypasses all of it.
A SESSION_SETUP carrying only an NTLM Type-1 (NtLmNegotiate) blob publishes
a fresh SMB2_SESSION_IN_PROGRESS session whose sess->user is still NULL
(->user is assigned later, by ntlm_authenticate()). Used as operation 1 of
a COMPOUND with operation 2 = TREE_CONNECT (related, SessionId=ULLONG_MAX,
\\host\IPC$), the tree-connect then runs on that IN_PROGRESS session and
reaches ksmbd_ipc_tree_connect_request(), which dereferences
user_name(sess->user) with sess->user == NULL (transport_ipc.c:687/701/704)
-> remote NULL-pointer dereference and a kernel Oops that wedges the ksmbd
worker for all clients.
Reject any non-first compound operation that lands on a session which is
not SMB2_SESSION_VALID, mirroring the validity the standalone lookup path
enforces. SESSION_SETUP itself legitimately runs on an IN_PROGRESS session,
but it is never carried as a non-first compound operation, so multi-leg
authentication is unaffected by this check.
CVSS v3.1 Base Metrics — Score 7.5 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh
Affected & Patched Versions
- Linux Linux Kernel >= 5.15.121 and < 5.15.211
- Linux Linux Kernel >= 6.1.36 and < 6.1.177
- Linux Linux Kernel >= 6.3.10 and < 6.4
- Linux Linux Kernel >= 6.4.1 and < 6.6.144
- Linux Linux Kernel >= 6.7 and < 6.12.95
- Linux Linux Kernel >= 6.13 and < 6.18.37
- Linux Linux Kernel >= 6.19 and < 7.0.14
- Linux Linux Kernel >= 7.1 and < 7.1.2
- Linux Linux Kernel
- Linux >= eb947403518ea3d93f6d89264bb1f5416bb0c7d0 and < 25ff12b82a376ff5c4583102a63d2456a6b9ebb9
- Linux >= 854156d12caa9d36de1cf5f084591c7686cc8a9d and < fc578523a72cb8b329d32070b95898e81613cc3f
- Linux >= 5005bcb4219156f1bf7587b185080ec1da08518e and < d2bbbb6c55812220fee5d801c275cc267ea3cbeb
- Linux >= 5005bcb4219156f1bf7587b185080ec1da08518e and < 8f0302fb691537d33ec8f668565257ea9d340ffe
- Linux >= 5005bcb4219156f1bf7587b185080ec1da08518e and < 7cad3ceaf679c55bc9946685dacafce78ce6b51a
- Linux >= 5005bcb4219156f1bf7587b185080ec1da08518e and < 06e1f05a1dbe8bbd054c0927b17fc0a61cc8bef7
- Linux >= 5005bcb4219156f1bf7587b185080ec1da08518e and < 5f983b864d3d473ac533b2f4f44a1bbe5dcbccf4
- Linux >= 5005bcb4219156f1bf7587b185080ec1da08518e and < 609ca17d869d04ba249e32cdcbf13c0b1c66f43c
- Linux d1066c1b3663401cd23c0d6e60cdae750ce00c0f
- Linux >= 5.15.121 and < 5.15.211
- Linux >= 6.1.36 and < 6.1.177
- Linux >= 6.3.10 and < 6.4
- Linux 6.4
- Linux Linux Kernel 5.15.211
- Linux Linux Kernel 6.1.177
- Linux Linux Kernel 6.4
- Linux Linux Kernel 6.6.144
- Linux Linux Kernel 6.12.95
- Linux Linux Kernel 6.18.37
- Linux Linux Kernel 7.0.14
- Linux Linux Kernel 7.1.2
- Linux 25ff12b82a376ff5c4583102a63d2456a6b9ebb9
- Linux fc578523a72cb8b329d32070b95898e81613cc3f
- Linux d2bbbb6c55812220fee5d801c275cc267ea3cbeb
- Linux 8f0302fb691537d33ec8f668565257ea9d340ffe
- Linux 7cad3ceaf679c55bc9946685dacafce78ce6b51a
- Linux 06e1f05a1dbe8bbd054c0927b17fc0a61cc8bef7
- Linux 5f983b864d3d473ac533b2f4f44a1bbe5dcbccf4
- Linux 609ca17d869d04ba249e32cdcbf13c0b1c66f43c
- Linux 5.15.211
- Linux 6.1.177
- Linux 6.4
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is high.
- Check whether you run Linux Linux Kernel and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Jul 19, 2026Published
- Aug 17, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Linux Linux Kernel CVEsYou are reading CVE-2026-53383. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
- Patchhttps://git.kernel.org/stable/c/06e1f05a1dbe8bbd054c0927b17fc0a61cc8bef7
- Patchhttps://git.kernel.org/stable/c/25ff12b82a376ff5c4583102a63d2456a6b9ebb9
- Patchhttps://git.kernel.org/stable/c/5f983b864d3d473ac533b2f4f44a1bbe5dcbccf4
- Patchhttps://git.kernel.org/stable/c/609ca17d869d04ba249e32cdcbf13c0b1c66f43c
- Patchhttps://git.kernel.org/stable/c/7cad3ceaf679c55bc9946685dacafce78ce6b51a
- Patchhttps://git.kernel.org/stable/c/8f0302fb691537d33ec8f668565257ea9d340ffe
- Patchhttps://git.kernel.org/stable/c/d2bbbb6c55812220fee5d801c275cc267ea3cbeb
- Patchhttps://git.kernel.org/stable/c/fc578523a72cb8b329d32070b95898e81613cc3f
Data last checked: Nov 22, 2026 23:12 UTC