CVE-2026-99289 · Runtime
NO FIX YET
A flaw in the Linux kernel's ksmbd SMB server lets a session reach freed memory when another session supersedes a non-durable open with the same AppInstanceId. The sources describe a use-after-free that can be triggered during SMB2 open handling, with the freed memory then written to.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Systems running the Linux kernel's ksmbd in-kernel SMB server with SMB2 clients connected; the sources do not list affected kernel versions. Hosts that do not run ksmbd are not affected by this description.
Not affected if ksmbd-not-enabled
Who cares file-server, ksmbd, linux-kernel, smb
Unknown from the sources.
Unknown from the sources.
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix app-instance non-durable supersede session UAF
ksmbd_close_fd_app_instance_id() supersedes a prior open that has the same AppInstanceId. It reaches that open's session through opinfo->sess. This pointer is not refcounted.
Session teardown detaches durable handles before it frees the session. It does not detach a non-durable open. That open still points at the session through opinfo->sess after the session is freed. Another session can supersede the open at the same time. The supersede then takes a write lock through the stale pointer, in the freed session's file table.
BUG: KASAN: slab-use-after-free in _raw_write_lock+0x71/0xd0 Call Trace: _raw_write_lock+0x71/0xd0 ksmbd_close_fd_app_instance_id+0xd9/0x670 [ksmbd] smb2_open+0x3e10/0xd910 [ksmbd] Freed by task 212: ksmbd_session_destroy+0x38d/0x480 [ksmbd]
Fix this by looking the session up by opinfo->session_id. The lookup returns a reference, as smb2_break_collect_channels() does. Recheck that opinfo->sess still points at it before using it.
Do the lookup without m_lock held. destroy_previous_session() takes m_lock under the session table lock, and taking them in the other order here would deadlock.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.