CVE-2026-52996

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix durable fd leak on ClientGUID mismatch in durable v2 open ksmbd_lookup_fd_cguid() returns a ksmbd_file with its refcount incremented via ksmbd_fp_get(). parse_durable_handle_context() in the DURABLE_REQ_V2 case properly releases this reference on every path inside the ClientGUID-match branch, either by calling ksmbd_put_durable_fd() or by transferring ownership to dh_info->fp for a successful reconnect. However, when an entry exists in the global file table with the same CreateGuid but a different ClientGUID, the code simply falls through to the new-open path without dropping the reference obtained from ksmbd_lookup_fd_cguid(). Per MS-SMB2 section 3.3.5.9.10 ("Handling the SMB2_CREATE_DURABLE_HANDLE_REQUEST_V2 Create Context"), the server MUST locate an Open whose Open.CreateGuid matches the request's CreateGuid AND whose Open.ClientGuid matches the ClientGuid of the connection that received the request. If no such Open is found, the server MUST continue with the normal open execution phase. A CreateGuid hit with a ClientGUID mismatch is therefore the "Open not found" case: proceeding with a new open is correct, but the reference obtained purely as a side effect of the lookup must not be leaked. Repeated requests that hit this mismatch pin global_ft entries, prevent __ksmbd_close_fd() from ever running for the corresponding files, and defeat the durable scavenger, leading to long-lived resource leaks. Release the reference in the mismatch path and clear dh_info->fp so subsequent logic does not mistake a non-matching lookup result for a reconnect target.

• CWE-401

• https://git.kernel.org/stable/c/06f709d0e531f3e54d88665dd426be3998a774e6Patch
• https://git.kernel.org/stable/c/407b6e699ba8b45b72cc265eed8a1bc8a7191609Patch
• https://git.kernel.org/stable/c/804054d19886ac6628883d82410f6ee42a818664Patch
• https://git.kernel.org/stable/c/8c4a0ef19c8264c150833131af34541495832cd0Patch
• https://git.kernel.org/stable/c/f31beef633fbf2b5af7805fa187a10bcff1d4b49Patch

Published

Jun 24, 2026

Last Modified

Jul 15, 2026

Status

Analyzed

• 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.

• CVE-2026-52990In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-52991In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-52992In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-52993In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-52994In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-52995In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-52997In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-52998In the Linux kernel, the following vulnerability has been re…7.5
• CVE-2026-52999In the Linux kernel, the following vulnerability has been re…9.1
• CVE-2026-5300Unauthenticated functionality in CoolerControl/coolercontro…9.1
• CVE-2026-53000In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-53001In the Linux kernel, the following vulnerability has been re…5.5