Affects the Linux kernel networking stack — widely deployed across servers, cloud, routers and embedded devices; can remotely crash hosts and disrupt operations.
CVE-2026-72323
Remote kernel panic via IGMP Use-After-Free in Linux kernel
Is CVE-2026-72323 being exploited?
Not confirmed. CVE-2026-72323 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.72% probability of exploitation in the next 30 days.
How severe is CVE-2026-72323?
CVE-2026-72323 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72323?
Yes. A fix has been recorded for CVE-2026-72323. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72323 affect?
CVE-2026-72323 affects Linux kernel (IGMP/inet subsystem), IPv4 IGMP-enabled hosts, Servers, routers, embedded devices running affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72323?
Apply vendor kernel security updates immediately; block IGMP at network edge if patching is delayed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attackers can send crafted IGMP queries to trigger a UAF in IGMP timer, causing kernel panic and host crash (remote DoS).
Immediate action required
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 7265c747eec415ca3109a6a14a419f7ae433b780
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < d107b4c4f8274763b7ea5ab05d45cef78e4b81ba
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 74b301f7f197517016befb5f5dfab01f7bc64be5
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 40a1e998cb266ed4cb529a0bb4fee2b0ba732702
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 165258303357e54b75fc19b341ae2a2b7c9e3910
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 75e984fe0cb9e7fbde0c8ee838c61ce8573d3ea3
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 8d4394ffa40508e0de72f464af351f6ca6a6cdc3
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 7b19c0f81ed1fdaec6bc522569be367199a9edf3
- affected2.6.12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.