HIGH Introduced in 7.2
ksmbd Channel UAF
CVE-2026-98870
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
KernelScan AI9.8CRITICAL
01Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: remove stale channels from all sessions on teardown ksmbd_sessions_deregister() removes a connection's channels from other sessions' channel lists only while conn->binding is still set: if (conn->binding) { hash_for_each_safe(sessions_table, ...) ksmbd_chann_del(conn, sess); } conn->binding is a transient flag: it is cleared once a binding SESSION_SETUP completes, and also by a subsequent non-binding SESSION_SETUP on the same connection (a reauthentication on a bound channel, or a new SessionId==0 setup). A connection that has bound a channel into another session's ksmbd_chann_list and then clears conn->binding leaves that channel behind when it disconnects: the channel, whose chann->conn points at the now freed struct ksmbd_conn, stays on the owner session's list. When the owning connection later tears down, the second loop dereferences the stale channel: xa_for_each(&sess->ksmbd_chann_list, chann_id, chann) if (chann->conn != conn) ksmbd_conn_set_exiting(chann->conn); /* freed */ which is a use-after-free write into the freed ksmbd_conn (the same stale channel is also walked by show_proc_session() through /proc). The session is leaked as well, because its channel list never empties. Remove the conn->binding gate so a connection always removes its channels from every session on teardown.
02KernelScan AI Analysis
Risk summary
A remote attacker who can connect to an SMB server running ksmbd can trigger a use-after-free in the kernel by performing a channel binding followed by reauthentication and disconnection. This leads to kernel memory corruption, potentially allowing arbitrary code execution, information disclosure, or denial of service. The vulnerability is reachable over the network without authentication in configurations that permit anonymous SMB session setup.
Vulnerability analysis
The ksmbd SMB server fails to clean up channel references from all sessions when a connection tears down. A connection's channels are only removed from other sessions' channel lists while a transient binding flag (conn->binding) is set, but this flag is cleared after the initial binding SESSION_SETUP completes or when a subsequent reauthentication occurs. If a client binds a channel, then reauthenticates (clearing the flag), and finally disconnects, the channel remains linked in the owning session's list with a pointer to the now-freed connection object. During later teardown, the kernel dereferences this stale pointer, writing to freed memory. The fix removes the conditional gate so channels are always unlinked from every session on disconnect, preventing the dangling reference.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 5.15 | 5.15.222 | 5.16 | f8200bb4994e |
| cip/6.1 | 7.2 | 6.1.189-cip61 | f8200bb4994e |
| cip/6.1-rt | 7.2 | 6.1.189-cip61-rt32 | f8200bb4994e |
| cip/6.12 | 7.2 | 6.12.111-cip32 | b145f9b56c87 |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Fixed in 6.12.111-cip32 |
| cip/6.1 | Fixed in 6.1.189-cip61 |
| cip/6.1-rt | Fixed in 6.1.189-cip61-rt32 |