CVE-2026-99290: ksmbd: fix use-after-free after a failed durable reconnect
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free after a failed durable reconnect
ksmbdreopendurablefd() republishes a detached durable handle in the reconnecting session's file table and takes no reference for that entry. If smb2open() then fails, cleanup relies on the final ksmbdfdput() to remove the volatile id.
Two reconnects of the same handle can both take a lookup reference before either attaches it. If the one that reopens first then fails and drops its references first, the other request makes the final put through ksmbdputdurablefd(). That frees the handle without removing the first session's table entry, so tearing that session down writes to freed memory.
BUG: KASAN: slab-use-after-free in closefiletableids+0x14d/0x740 [ksmbd] Call Trace: closefiletableids+0x14d/0x740 [ksmbd] ksmbddestroyfiletable+0x76/0x100 [ksmbd] ksmbdsessiondestroy+0xf8/0x480 [ksmbd] ksmbddisposesessions+0x13e/0x200 [ksmbd] ksmbdconnsessionscleanup+0x4c3/0x6d0 [ksmbd] Freed by task 1030: ksmbdclosefd+0x97d/0x1000 [ksmbd] smb2open+0x14eb/0xd9f0 [ksmbd]
Commit 3515503322f4 ("ksmbd: fix durable reconnect error path file lifetime") handles a final put made by the reconnecting request, but not one made by another holder.
Remove the volatile id under the file-table lock on this error path, before the references are dropped, as ksmbdclosefd() does on the requestopen path just above. Removal then no longer depends on which holder makes the final put. The stale comment in the reconnect cleanup is updated to match. A successful reconnect is unchanged.