Linux kernel networking bug affects widespread servers, containers, and network appliances; exploitation can disrupt infrastructure or lead to kernel compromise.
CVE-2026-72319
Linux ipvs ICMP error handling flaw enables kernel memory corruption, DoS, or RCE.
Is CVE-2026-72319 being exploited?
Not confirmed. CVE-2026-72319 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.74% probability of exploitation in the next 30 days.
How severe is CVE-2026-72319?
CVE-2026-72319 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-72319?
Yes. A fix has been recorded for CVE-2026-72319. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72319 affect?
CVE-2026-72319 affects Linux kernel (ipvs module), Linux-based servers, Containers using host kernel, Network appliances/routers using Linux. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72319?
Apply vendor kernel patches, reboot affected hosts, and block/untrusted ICMP on tunnel endpoints.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted tunneled ICMP errors can trigger kernel memory corruption, causing remote DoS and potential privilege escalation or RCE.
Immediate action required
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < 19657b3a17b774ae4e2f2635b5ae8638c9344a40
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < dac813101914c21219ac221a60a31a11bc90e7ec
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < dd22f74a09e25ca298ced0a3763ef353242cb78d
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < 9bc9b95aee2b2e3f1301a16a67ee504960402875
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < a735f9964a3d9ed97daf9b08507f8b5bcafe6326
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < 8f48cfe657409fb5c7ba0521b14da6d47546d9cf
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < 92185d6f7819bc558939ae83de7b1abe90e3b5c2
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < 3f7a535ff0fa627a0132803e4c2f903ceffcbc1c
- affected3.7
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.