CVE-2026-72321: ipv4: igmp: Fix potential memory leaks in igmp_mod_timer() and igmp_stop_timer()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 2d0effadf8d2cc9d006e4c4ab0ab6737aed28d77, 3546deaa0c30a14c7cdb5dc8f2432cb428f0cd36, 40d6360ccf9bcbe17b5cb248a84e8e004aac2faa; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 2d0effadf8d2cc9d006e4c4ab0ab6737aed28d77, 3546deaa0c30a14c7cdb5dc8f2432cb428f0cd36, 40d6360ccf9bcbe17b5cb248a84e8e004aac2faa; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ipv4: igmp: Fix potential memory leaks in igmp_mod_timer() and igmp_stop_timer() When a timer is deleted and not re-armed in igmp_mod_timer(), or stopped in igmp_stop_timer(), the code currently decrements the reference counter of the multicast list entry @im using refcount_dec(&im->refcnt). However, both functions can be called from the RCU reader path: - igmp_mod_timer() via igmp_heard_query() -> for_each_pmc_rcu() - igmp_stop_timer() via igmp_rcv() -> igmp_heard_report() If the group im was concurrently removed from the list by ip_mc_dec_group(), its reference count might have already been decremented to 1. In this case, timer_delete() succeeds, and refcount_dec() decrements the refcount from 1 to 0. Since refcount_dec() does not free the object when it hits 0 (unlike ip_ma_put()), the im structure is leaked. Fix this by using ip_ma_put(im) instead of refcount_dec(&im->refcnt), and deferring the put until after the spinlock is released.
- Published
- Aug 15, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before d4fe30f4671033a27fba077b3976dc113ffc0169affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2d0effadf8d2cc9d006e4c4ab0ab6737aed28d77affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 40d6360ccf9bcbe17b5cb248a84e8e004aac2faaaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before f60ec3058a85447008b88b762c859d336163acb3affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 95128dc74425ec19ed4f2077ccc651e791ff4b75affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 3546deaa0c30a14c7cdb5dc8f2432cb428f0cd36affected · git
- before 2.6.12not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.192-1 | 6.1.192-1 |
| Debian:12 | linux-6.12 | before 6.12.115-2~deb12u1 | 6.12.115-2~deb12u1 |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72319Aug 15, 2026 · ipvs: ensure inner headers in ICMP errors are in headroom39Monitor
- ← EarlierCVE-2026-72320Aug 15, 2026 · netfilter: nft_lookup: fix catchall element handling with inverted lookups36Monitor
- Later →CVE-2026-72322Aug 15, 2026 · ipv6: mcast: Fix potential UAF in MLD delayed work39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2d0effadf8d2cc9d006e4c4ab0ab6737aed28d77 | Vendor (CNA) |
| Linux Linux | 3546deaa0c30a14c7cdb5dc8f2432cb428f0cd36 | Vendor (CNA) |
| Linux Linux | 40d6360ccf9bcbe17b5cb248a84e8e004aac2faa | Vendor (CNA) |
| Linux Linux | 95128dc74425ec19ed4f2077ccc651e791ff4b75 | Vendor (CNA) |
| Linux Linux | d4fe30f4671033a27fba077b3976dc113ffc0169 | Vendor (CNA) |
| Linux Linux | f60ec3058a85447008b88b762c859d336163acb3 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.1.5-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.115-2~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3546deaa0c30a14c7cdb5dc8f2432cb428f0cd36
- git.kernel.org/stable/c/40d6360ccf9bcbe17b5cb248a84e8e004aac2faa
- git.kernel.org/stable/c/95128dc74425ec19ed4f2077ccc651e791ff4b75
- git.kernel.org/stable/c/d4fe30f4671033a27fba077b3976dc113ffc0169
- git.kernel.org/stable/c/f60ec3058a85447008b88b762c859d336163acb3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.