Vulnerability · Published Sep 16, 2026 · Assigned by Linux

CVE-2026-89788ksmbd: fix tree connection use-after-free in smb2_tree_connect()

Critical 9.8

In plain English

A critical-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.6% (higher than 51% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)9.8Critical
Exploit odds (30 days)0.6%top 49.0% 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 tree connection use-after-free in smb2_tree_connect() ksmbd_tree_conn_connect() publishes a new tree connection in sess->tree_conns with a single reference and returns its pointer to smb2_tree_connect(). The handler continues to initialize the object and build the response after publication. A concurrent session logoff can erase the connection and drop that reference, freeing the object while the handler still uses it. BUG: KASAN: slab-use-after-free in smb2_tree_connect+0xe3d/0xf90 smb2_tree_connect (fs/smb/server/smb2pdu.c:2872) handle_ksmbd_work process_one_work worker_thread kthread After xa_store() succeeds, take a second reference before releasing tree_conns_lock. The original reference belongs to the xarray entry and the second belongs to the creating smb2_tree_connect() handler. Keep the references balanced in every path: - On normal exit or an error after publication, smb2_tree_connect() drops its creator reference. Error cleanup also calls ksmbd_tree_conn_disconnect(), which drops the xarray reference only if it removes the exact entry. - SMB2 TREE_DISCONNECT uses the same helper to remove the entry and drop its xarray reference. The request's existing lookup reference remains owned by the request and is released by the existing cleanup. - Session LOGOFF removes each entry and drops its xarray reference. If it wins the race, later cleanup sees that the entry is gone and does not drop that reference again. To enforce this ownership, claim the disconnected state and erase the exact entry atomically under tree_conns_lock. This guarantees one drop for the xarray reference and one drop by each in-flight user, regardless of which teardown path wins. If logoff removes the entry before initialization completes, fail the connect instead of marking the detached object TREE_CONNECTED.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-89788
Debian:13linux6.12.115-2DEBIAN-CVE-2026-89788
Debian:14linux7.2.6-1DEBIAN-CVE-2026-89788
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1038.42UBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-89788
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-89788
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-89788
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-89788

Affected products (as reported)

VendorProductVersions
Linux Linux 7b58ee8d0b91359554cf219cd4f33872ea2afd66 – before 63f5939b50470ef4d245c16d2098376b952beb5133b235a6e6ebe0f05f3586a71e8d281d00f71e2e – before ca3a3984bf445aaec69f6937f11e560d4b84936533b235a6e6ebe0f05f3586a71e8d281d00f71e2e – before bd58a52738f7576ee5f5eb74243df13f902c805133b235a6e6ebe0f05f3586a71e8d281d00f71e2e – before 4e30fbd26e84efa2e5cbec4eb11e126ac0c7931333b235a6e6ebe0f05f3586a71e8d281d00f71e2e – before b5ec6c462aab1062cf5d1e667ba7c6442f737055dd45db4d9bbc8f122a9b4db5ce94ae29fcf03d3c6.1.71 – before 6.1.1915.15.145 – before 5.16
Linux Linux 6.6

References