Linux
ipv4: igmp: Fix potential UAF in igmp_gq_start_timer()
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 7265c747eec415ca3109a6a14a419f7ae433b780
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < d107b4c4f8274763b7ea5ab05d45cef78e4b81ba
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 74b301f7f197517016befb5f5dfab01f7bc64be5
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 40a1e998cb266ed4cb529a0bb4fee2b0ba732702
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 165258303357e54b75fc19b341ae2a2b7c9e3910
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 75e984fe0cb9e7fbde0c8ee838c61ce8573d3ea3
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 8d4394ffa40508e0de72f464af351f6ca6a6cdc3
- >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 7b19c0f81ed1fdaec6bc522569be367199a9edf3
Fixed in 7265c747eec415ca3109a6a14a419f7ae433b780, d107b4c4f8274763b7ea5ab05d45cef78e4b81ba, 74b301f7f197517016befb5f5dfab01f7bc64be5, 40a1e998cb266ed4cb529a0bb4fee2b0ba732702, 165258303357e54b75fc19b341ae2a2b7c9e3910, 75e984fe0cb9e7fbde0c8ee838c61ce8573d3ea3, 8d4394ffa40508e0de72f464af351f6ca6a6cdc3, 7b19c0f81ed1fdaec6bc522569be367199a9edf3
- 2.6.12
Fixed in 0, 5.10.269, 5.15.220, 6.1.187, 6.6.145, 6.12.97, 6.18.40, 7.1.5, 7.2
Mitigation
Upgrade Linux to 7265c747eec415ca3109a6a14a419f7ae433b780 or d107b4c4f8274763b7ea5ab05d45cef78e4b81ba or 74b301f7f197517016befb5f5dfab01f7bc64be5 or 40a1e998cb266ed4cb529a0bb4fee2b0ba732702 or 165258303357e54b75fc19b341ae2a2b7c9e3910 or 75e984fe0cb9e7fbde0c8ee838c61ce8573d3ea3 or 8d4394ffa40508e0de72f464af351f6ca6a6cdc3 or 7b19c0f81ed1fdaec6bc522569be367199a9edf3 or later.
Upgrade Linux to 0 or 5.10.269 or 5.15.220 or 6.1.187 or 6.6.145 or 6.12.97 or 6.18.40 or 7.1.5 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.