CVE-2026-72321: ipv4: igmp: Fix potential memory leaks in igmp_mod_timer() and igmp_stop_timer()
In the Linux kernel, the following vulnerability has been resolved:
ipv4: igmp: Fix potential memory leaks in igmpmodtimer() and igmpstoptimer()
When a timer is deleted and not re-armed in igmpmodtimer(), or stopped in igmpstoptimer(), the code currently decrements the reference counter of the multicast list entry @im using refcountdec(&im->refcnt).
However, both functions can be called from the RCU reader path: - igmpmodtimer() via igmpheardquery() -> foreachpmcrcu() - igmpstoptimer() via igmprcv() -> igmpheardreport()
If the group im was concurrently removed from the list by ipmcdecgroup(), its reference count might have already been decremented to 1.
In this case, timerdelete() succeeds, and refcountdec() decrements the refcount from 1 to 0. Since refcountdec() does not free the object when it hits 0 (unlike ipmaput()), the im structure is leaked.
Fix this by using ipmaput(im) instead of refcountdec(&im->refcnt), and deferring the put until after the spinlock is released.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-aws-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-fde-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1016.16~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38~24.04.4 - Upgrade
Upgrade
ubuntu/linux-oracle-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1013.13~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-38.38 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.0.0-1016.16 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 7.0.0-1008.9 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1013.13 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.114 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.40 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.1.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.1.5-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.12-1Fixed in 7.2.14-1 - Compensating control
In the Linux kernel IPv4 IGMP code, replace refcount_dec(&im->refcnt) with ip_ma_put(im) in igmp_mod_timer() and igmp_stop_timer(), and defer the ip_ma_put(im) call until after the spinlock is released.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72321?
CVE-2026-72321 has a risk severity score of 15.
How do I fix CVE-2026-72321?
To fix CVE-2026-72321, ensure that your Linux kernel is updated to the latest version where this vulnerability is patched.
What systems are affected by CVE-2026-72321?
CVE-2026-72321 affects versions of the Linux kernel that use IPv4 IGMP features.
What types of attacks can CVE-2026-72321 lead to?
CVE-2026-72321 may lead to memory leaks, which can affect system stability and performance.
When was CVE-2026-72321 published?
CVE-2026-72321 was published on August 15, 2026.