{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-99290","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-09-25T10:25:14.406Z","datePublished":"2026-11-16T09:59:19.483Z","dateUpdated":"2026-11-19T13:52:08.526Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-11-19T13:52:08.526Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free after a failed durable reconnect\n\nksmbd_reopen_durable_fd() republishes a detached durable handle in the\nreconnecting session's file table and takes no reference for that entry.\nIf smb2_open() then fails, cleanup relies on the final ksmbd_fd_put() to\nremove the volatile id.\n\nTwo reconnects of the same handle can both take a lookup reference before\neither attaches it. If the one that reopens first then fails and drops\nits references first, the other request makes the final put through\nksmbd_put_durable_fd(). That frees the handle without removing the first\nsession's table entry, so tearing that session down writes to freed\nmemory.\n\n  BUG: KASAN: slab-use-after-free in __close_file_table_ids+0x14d/0x740 [ksmbd]\n  Call Trace:\n   __close_file_table_ids+0x14d/0x740 [ksmbd]\n   ksmbd_destroy_file_table+0x76/0x100 [ksmbd]\n   ksmbd_session_destroy+0xf8/0x480 [ksmbd]\n   ksmbd_dispose_sessions+0x13e/0x200 [ksmbd]\n   ksmbd_conn_sessions_cleanup+0x4c3/0x6d0 [ksmbd]\n  Freed by task 1030:\n   __ksmbd_close_fd+0x97d/0x1000 [ksmbd]\n   smb2_open+0x14eb/0xd9f0 [ksmbd]\n\nCommit 3515503322f4 (\"ksmbd: fix durable reconnect error path file\nlifetime\") handles a final put made by the reconnecting request, but not\none made by another holder.\n\nRemove the volatile id under the file-table lock on this error path,\nbefore the references are dropped, as ksmbd_close_fd() does on the\nrequest_open path just above. Removal then no longer depends on which\nholder makes the final put. The stale comment in the reconnect cleanup\nis updated to match. A successful reconnect is unchanged."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.5,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:N - A remote client sends SMB2 CREATE on the TCP connection accepted by ksmbd_tcp_new_connection and read in ksmbd_conn_handler_loop. parse_durable_handle_context() in smb2_open() takes the DH2C/DHnC persistent id from that request, and ksmbd_reopen_durable_fd() republishes the detached handle.\nAC:H - The stale volatile id is left behind only when smb2_open() fails after ksmbd_reopen_durable_fd() succeeds, in ksmbd_override_fsids() or ksmbd_vfs_getattr(), before request_open is set. The client can overlap a second lookup, but cannot force that credential allocation or getattr to fail.\nPR:L - __handle_ksmbd_work() requires smb2_check_user_session() and smb2_get_ksmbd_tcon() before smb2_open(), and the reopen that publishes the id must pass ksmbd_vfs_compare_durable_owner() in smb2_check_durable_oplock(). That is the authenticated handle owner, not a pre-auth CREATE.\nUI:N - The client opens its own durable handle, drops that connection so session_fd_check() preserves it, and sends the reconnecting SMB2 CREATEs. No other principal has to open a file or approve the reconnect.\nS:U - The dangling pointer is a ksmbd_file in the host ksmbd_file_cache, and ksmbd_session_destroy() corrupts that kernel object. The bug does not cross a guest/host or IOMMU boundary.\nC:H - ksmbd_put_durable_fd() frees the handle in __ksmbd_close_fd() with kmem_cache_free(). Session teardown then loads that idr pointer in __close_file_table_ids() and reads refcount, f_ci, and conn; a reused slot lets those reads follow attacker-influenced kernel pointers.\nI:H - __close_file_table_ids() writes the freed ksmbd_file, storing volatile_id, locking fp->f_ci, and running list_del_init() on fp->node. Once the ksmbd_file_cache slot is reused, that path corrupts a live object, including its connection reference.\nA:H - ksmbd_session_destroy() reaches the dangling id through ksmbd_destroy_file_table() and __close_file_table_ids() and touches the ksmbd_file already freed from smb2_open(), which is the slab-use-after-free that oopses the kernel."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/smb/server/smb2pdu.c","fs/smb/server/vfs_cache.c","fs/smb/server/vfs_cache.h"],"versions":[{"version":"c8efcc786146a951091588e5fa7e3c754850cb3c","lessThan":"5078a4e41b29acdf6be52e4a7cc8a59c2a72a471","status":"affected","versionType":"git"},{"version":"c8efcc786146a951091588e5fa7e3c754850cb3c","lessThan":"bd47ee501b6ac4a26ae41f780a43b7967302a269","status":"affected","versionType":"git"},{"version":"c8efcc786146a951091588e5fa7e3c754850cb3c","lessThan":"edacf65866a9f397438d5b9ff9f43312b29b4b3c","status":"affected","versionType":"git"},{"version":"c8efcc786146a951091588e5fa7e3c754850cb3c","lessThan":"248b5819591c577727930e4e255a455235fab50a","status":"affected","versionType":"git"},{"version":"8df4bcdb0a4232192b2445256c39b787d58ef14d","status":"affected","versionType":"git"},{"version":"6.6.32","lessThan":"6.7","status":"affected","versionType":"semver"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/smb/server/smb2pdu.c","fs/smb/server/vfs_cache.c","fs/smb/server/vfs_cache.h"],"versions":[{"version":"6.9","status":"affected"},{"version":"0","lessThan":"6.9","status":"unaffected","versionType":"semver"},{"version":"6.12.117","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.61","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.3.2","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.9","versionEndExcluding":"6.12.117"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.9","versionEndExcluding":"6.18.61"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.9","versionEndExcluding":"7.3.2"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.9","versionEndExcluding":"7.4-rc1"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.6.32"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/5078a4e41b29acdf6be52e4a7cc8a59c2a72a471"},{"url":"https://git.kernel.org/stable/c/bd47ee501b6ac4a26ae41f780a43b7967302a269"},{"url":"https://git.kernel.org/stable/c/edacf65866a9f397438d5b9ff9f43312b29b4b3c"},{"url":"https://git.kernel.org/stable/c/248b5819591c577727930e4e255a455235fab50a"}],"title":"ksmbd: fix use-after-free after a failed durable reconnect","x_generator":{"engine":"bippy-1.2.0"}}}}