Vulnerability · Published Aug 15, 2026 · Assigned by Linux

CVE-2026-72323ipv4: igmp: Fix potential UAF in igmp_gq_start_timer()

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 45.7% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() A race condition exists between device teardown (inetdev_destroy) and incoming IGMP query processing (igmp_rcv), leading to a Use-After-Free in the IGMP timer callback. During device destruction, inetdev_destroy() drops the primary reference to in_device, which can drop its refcount to 0. The actual freeing of in_device memory is deferred via RCU (using call_rcu()). Concurrently, igmp_rcv() runs under RCU read lock and obtains the in_device pointer. Because the memory is RCU-protected, CPU-0 can safely dereference in_device even if its refcount has hit 0. However, if CPU-0 calls igmp_gq_start_timer() and re-arms the timer, it attempts to acquire a reference using in_dev_hold(). This increments the refcount from 0 to 1, triggering a "refcount_t: addition on 0" warning. Since the in_device memory is still scheduled to be freed after the RCU grace period (as the free callback does not check the refcount again), the device is freed while the timer is still armed. When the timer expires, it accesses the freed memory, causing a kernel panic. Fix this by using refcount_inc_not_zero() (via a new helper in_dev_hold_safe()) to prevent acquiring a reference if the device is already being destroyed. If the refcount is 0, we do not arm the timer. A similar issue in IPv6 MLD is fixed in a subsequent patch.

Affected packages & fixed versions

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

Affected products (as reported)

VendorProductVersions
Linux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 7265c747eec415ca3109a6a14a419f7ae433b7801da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before d107b4c4f8274763b7ea5ab05d45cef78e4b81ba1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 74b301f7f197517016befb5f5dfab01f7bc64be51da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 40a1e998cb266ed4cb529a0bb4fee2b0ba7327021da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 165258303357e54b75fc19b341ae2a2b7c9e39101da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 75e984fe0cb9e7fbde0c8ee838c61ce8573d3ea31da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 8d4394ffa40508e0de72f464af351f6ca6a6cdc31da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 7b19c0f81ed1fdaec6bc522569be367199a9edf3
Linux Linux 2.6.12

References