Vulnerability · Published Aug 15, 2026 · Assigned by Linux

CVE-2026-72422ksmbd: fix use-after-free of conn->preauth_info in concurrent SMB2 NEGOTIATE

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

Severity (CVSS 3.1)9.8Critical
Exploit odds (30 days)0.7%top 46.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 use-after-free of conn->preauth_info in concurrent SMB2 NEGOTIATE conn->preauth_info is shared connection state (struct preauth_integrity_info, kmalloc-96) that is allocated and freed by the SMB2 NEGOTIATE handler and read by the response send path. smb2_handle_negotiate() allocates conn->preauth_info, and on a deassemble_neg_contexts() failure kfrees it and sets it to NULL. Both the allocation and the free/NULL happen under ksmbd_conn_lock(conn) (the connection srv_mutex), which is held across the whole handler body. The response send path smb3_preauth_hash_rsp(), called from the send: block of __handle_ksmbd_work(), reads conn->preauth_info and dereferences conn->preauth_info->Preauth_HashValue (via ksmbd_gen_preauth_integrity_hash()) without taking conn_lock. When a client drives two SMB2 NEGOTIATE requests on the same connection, one worker can free conn->preauth_info on the failing-negotiate path while a concurrent send-path worker is reading it, producing a slab use-after-free read (KASAN-confirmed). The send-path read tested conn->preauth_info for NULL but raced with the free that occurs between the NULL check and the dereference, so the NULL guard alone does not close the window. Serialize the NEGOTIATE-branch read in smb3_preauth_hash_rsp() under ksmbd_conn_lock(conn) and re-check conn->preauth_info inside the lock. Because the negotiate handler holds conn_lock across its kfree + NULL assignment, a reader that also takes conn_lock either runs fully before the allocation or fully after the NULL store, and can never observe the freed-but-not-yet-NULLed pointer. ksmbd_gen_preauth_integrity_hash() takes no locks itself (it only computes a SHA-512 over the buffer), so no lock-ordering inversion is introduced, and conn_lock is a sleepable mutex which is safe on this send path (it already performs network I/O).

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.180-1DEBIAN-CVE-2026-72422
Debian:13linux6.12.100-1DEBIAN-CVE-2026-72422
Debian:14linux7.1.5-1DEBIAN-CVE-2026-72422
Ubuntu:22.04:LTSlinux5.15.0-198.208UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux6.8.0-147.147UBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux7.0.0-34.34UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-aws5.15.0-1117.124UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-aws6.8.0-1067.70UBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-aws7.0.0-1013.13UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-azure5.15.0-1123.132UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-azure6.8.0-1071.79UBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-azure7.0.0-1017.17UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1017.17~24.04.1UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1122.131UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1069.76UBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1016.16UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-gcp5.15.0-1118.128UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-gcp6.8.0-1071.79UBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-gcp7.0.0-1013.13UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-gke5.15.0-1113.119UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-gke6.8.0-1066.74UBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-gke7.0.0-1007.8UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1100.108UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1052.56UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-34.34~24.04.1UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-ibm5.15.0-1111.115UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-ibm6.8.0-1067.68UBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-ibm7.0.0-1014.14UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1112.118UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-kvm5.15.0-1109.114UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-195.205UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-147.147.1UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1112.113UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1024.25~24.04.1UBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2022.23UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1070.72UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1035.38UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1059.59UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1014.14UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-oracle5.15.0-1114.120UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-oracle6.8.0-1064.67UBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-oracle7.0.0-1012.12UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1012.12~24.04.1UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-raspi7.0.0-1020.20UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-realtime7.0.0-34.34.1UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-72422
Ubuntu:26.04:LTSlinux-riscv7.0.0-34.34.1UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-34.34.1~24.04.1UBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-vmware6.8.0-1008.8UBUNTU-CVE-2026-72422
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-72422
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1080.84UBUNTU-CVE-2026-72422

Affected products (as reported)

VendorProductVersions
Linux Linux dd4e4c811898410e6a3ae3b63207b7c542860907 – before c7bef84740d1d57848c74f6f5b996606e43ea4feaa7253c2393f6dcd6a1468b0792f6da76edad917 – before d0a469122e7bf8338fec1949fb1e8e1290ed8caaaa7253c2393f6dcd6a1468b0792f6da76edad917 – before 7470511d085af1c7a043a60e53d52b512d5a10b1aa7253c2393f6dcd6a1468b0792f6da76edad917 – before 16a1ecf39c217e3d164bd32ef2a4f650abc067faaa7253c2393f6dcd6a1468b0792f6da76edad917 – before 77bb0bbfcc4e777ca653174689e5e363f8ee63d1aa7253c2393f6dcd6a1468b0792f6da76edad917 – before 1c89da3baa2b1f269178afa87dc30479b8535776aa7253c2393f6dcd6a1468b0792f6da76edad917 – before 0c054227479ed7e36ebccb3a558bc0ef698264f68a8315a5960bd2b5ffc75f44fc089e57c3b17c44
Linux Linux 6.0

References