CVE-2026-99290
Description
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.
Timeline
- 2026-11-16Published by the CNA09:59 UTC
- 2026-11-16Published in NVD10:17 UTC · 17 minutes after the CNA
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| linux linux | from 6.6.32 before 6.7fixed in 6.7 | 6.7 |
| linux linux_kernel | from 6.9 before 6.12.117fixed in 6.12.117from 6.9 before 6.18.61fixed in 6.18.61from 6.9 before 7.3.2fixed in 7.3.2from 6.9 before 7.4-rc1fixed in 7.4-rc1from 6.6.32no fix listed | 6.12.1176.18.617.3.27.4-rc1not listed |
References
- https://git.kernel.org/stable/c/248b5819591c577727930e4e255a455235fab50a
- https://git.kernel.org/stable/c/5078a4e41b29acdf6be52e4a7cc8a59c2a72a471
- https://git.kernel.org/stable/c/bd47ee501b6ac4a26ae41f780a43b7967302a269
- https://git.kernel.org/stable/c/edacf65866a9f397438d5b9ff9f43312b29b4b3c
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2026-99290'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2026-99290'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2026-99290'curl 'https://api.contrastcyber.com/cve_products/CVE-2026-99290'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).