ksmbd: fix use-after-free after a failed durable reconnect
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel edacf65866a9f397438d5b9ff9f43312b29b4b3c, Kernel 6.7, Kernel 248b5819591c577727930e4e255a455235fab50a and 5 more.
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free after a failed durable reconnect ksmbd_reopen_durable_fd() republishes a detached durable handle in the reconnecting session's file table and takes no reference for that entry. If smb2_open() then fails, cleanup relies on the final ksmbd_fd_put() 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 ksmbd_put_durable_fd(). 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 __close_file_table_ids+0x14d/0x740 [ksmbd] Call Trace: __close_file_table_ids+0x14d/0x740 [ksmbd] ksmbd_destroy_file_table+0x76/0x100 [ksmbd] ksmbd_session_destroy+0xf8/0x480 [ksmbd] ksmbd_dispose_sessions+0x13e/0x200 [ksmbd] ksmbd_conn_sessions_cleanup+0x4c3/0x6d0 [ksmbd] Freed by task 1030: __ksmbd_close_fd+0x97d/0x1000 [ksmbd] smb2_open+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 ksmbd_close_fd() does on the request_open 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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=c8efcc786146a951091588e5fa7e3c754850cb3c <edacf65866a9f397438d5b9ff9f43312b29b4b3c, >=6.6.32 <6.7, >=c8efcc786146a951091588e5fa7e3c754850cb3c <248b5819591c577727930e4e255a455235fab50a, >=c8efcc786146a951091588e5fa7e3c754850cb3c <5078a4e41b29acdf6be52e4a7cc8a59c2a72a471, >=c8efcc786146a951091588e5fa7e3c754850cb3c <bd47ee501b6ac4a26ae41f780a43b7967302a269, =6.9, =8df4bcdb0a4232192b2445256c39b787d58ef14d | edacf65866a9f397438d5b9ff9f43312b29b4b3c, 6.7, 248b5819591c577727930e4e255a455235fab50a, 5078a4e41b29acdf6be52e4a7cc8a59c2a72a471, bd47ee501b6ac4a26ae41f780a43b7967302a269 |
| linux-kernel: Kernel | >=6.19.0 <7.3.2, >=6.6.32 <6.7, >=6.9.0 <6.12.117, >=6.13.0 <6.18.61 | 7.3.2, 6.7, 6.12.117, 6.18.61 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket