CVE-2026-99289
Last modified
CVE-2026-99289 is a vulnerability of currently unknown severity. 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.
Description
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 16c30649709d949b439273e61769028b1e706327, < a5b190b352b0ba85f4debe436f42950ced10fadb; >= 16c30649709d949b439273e61769028b1e706327, < f728cfee6929057087c303d07d7a6a7c61196b48 |
| Linux | Linux | 7.2 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-99289?
How severe is CVE-2026-99289?
How do I fix CVE-2026-99289?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-99283In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99284In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99285In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99286In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99287In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99288In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9929Inappropriate implementation in WebGL in Google Chrome on An…4.3
- CVE-2026-99290In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99291In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99292In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99293In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99294In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-99289?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
