PT-2026-151750
CVE-2026-99539
·
Published
2026-11-19
·
Updated
2026-11-19
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix session reference leak on compounded SESSION SETUP
A compound request can place SESSION SETUP after another command. That
earlier command leaves a reference to its session in work->sess.
smb2 sess setup() then overwrites work->sess with the session it looks up
or creates, and the dispatcher later puts work->sess only once. The
inherited reference is never dropped. That leaks the session, together
with its setup connection and socket, and every repeat of the compound
leaks another.
unreferenced object (size 512):
kmalloc cache noprof+0x32c/0x3a0
ksmbd smb2 session create+0xf6/0x9c0 [ksmbd]
smb2 sess setup+0xda4/0x6280 [ksmbd]
handle ksmbd work+0x88c/0x1cb0 [ksmbd]
Save the inherited session on entry. After the request has been
processed, release it once, but only when smb2 sess setup() has replaced
work->sess with its own session or cleared it. Do this after
ksmbd conn unlock() so the put does not run under srv mutex. An error path
may instead leave the inherited session in work->sess. Keep it there, so
the dispatcher still puts it and the error response is still signed or
encrypted with it as before.
Found an issue in the description? Have something to add? Feel free to write us 👾