Vulnerability · Published Jun 24, 2026 · Assigned by Linux

CVE-2026-52996ksmbd: fix durable fd leak on ClientGUID mismatch in durable v2 open

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 93.4% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.94-1DEBIAN-CVE-2026-52996
Debian:14linux7.0.10-1DEBIAN-CVE-2026-52996
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux7.0.0-28.28UBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-52996
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-aws7.0.0-1009.9UBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-52996
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-azure7.0.0-1010.10UBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-52996
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1009.9UBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-52996
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-gcp7.0.0-1008.8UBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-gke7.0.0-1003.4UBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-ibm7.0.0-1010.10UBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1016.16UBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2016.16UBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1009.9UBUNTU-CVE-2026-52996
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-oracle7.0.0-1008.8UBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-52996
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-raspi7.0.0-1015.15UBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-52996
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-realtime7.0.0-28.28.1UBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-52996
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-52996
Ubuntu:26.04:LTSlinux-riscv7.0.0-28.28.1UBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-52996
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-28.28.1~24.04.3UBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-52996
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-52996

Affected products (as reported)

VendorProductVersions
Linux Linux 8df4bcdb0a4232192b2445256c39b787d58ef14d – before 407b6e699ba8b45b72cc265eed8a1bc8a7191609c8efcc786146a951091588e5fa7e3c754850cb3c – before f31beef633fbf2b5af7805fa187a10bcff1d4b49c8efcc786146a951091588e5fa7e3c754850cb3c – before 06f709d0e531f3e54d88665dd426be3998a774e6c8efcc786146a951091588e5fa7e3c754850cb3c – before 8c4a0ef19c8264c150833131af34541495832cd0c8efcc786146a951091588e5fa7e3c754850cb3c – before 804054d19886ac6628883d82410f6ee42a8186646.6.32 – before 6.6.141
Linux Linux 6.9

References