CVE-2026-72323
Linux kernel vulnerability
- Published15 Aug 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/165258303357e54b75fc19b341ae2a2b7c9e3910
- https://git.kernel.org/stable/c/40a1e998cb266ed4cb529a0bb4fee2b0ba732702
- https://git.kernel.org/stable/c/7265c747eec415ca3109a6a14a419f7ae433b780
- https://git.kernel.org/stable/c/74b301f7f197517016befb5f5dfab01f7bc64be5
- https://git.kernel.org/stable/c/75e984fe0cb9e7fbde0c8ee838c61ce8573d3ea3
- https://git.kernel.org/stable/c/7b19c0f81ed1fdaec6bc522569be367199a9edf3
- https://git.kernel.org/stable/c/8d4394ffa40508e0de72f464af351f6ca6a6cdc3
- https://git.kernel.org/stable/c/d107b4c4f8274763b7ea5ab05d45cef78e4b81ba
Frequently asked
Is CVE-2026-72323 being actively exploited?
CVE-2026-72323 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.72%.
How severe is CVE-2026-72323?
CVE-2026-72323 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.72% probability of exploitation.
How do I fix CVE-2026-72323?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-72323 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.