Affects the Linux kernel (widely deployed); kernel memory corruption can lead to host compromise and impacts IPVS users including Kubernetes clusters—high organizational impact.
CVE-2026-74669
Linux kernel IPVS bug allows kernel memory corruption via crafted IPv4/ICMP packets
Is CVE-2026-74669 being exploited?
Not confirmed. CVE-2026-74669 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.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-74669?
CVE-2026-74669 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-74669?
Yes. A fix has been recorded for CVE-2026-74669. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74669 affect?
CVE-2026-74669 affects Linux kernel (IPVS / ip_vs_in_icmp), Systems using IPVS (load balancers, kube-proxy in IPVS mode), Linux hosts and containers with IPVS enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74669?
Update Linux kernel to vendor fixed release; restrict/inspect ICMP and limit IPVS exposure.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted IPv4/ICMP packets trigger a kernel stack out-of-bounds write in IPVS, enabling crashes, privilege escalation, or potential remote kernel code execution.
Immediate action required
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < 79ffa99202c944467e28b13b513bf2998732edff
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < c9413b50204738fbc429bb86bf01353c393a6c28
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < 37c61b3745129cbd682c557b51345828120972e5
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < ed246dd85ebf27c1f6b7897834d40786c0ca3006
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < 6f46fc460e9316062bdcdf89199eb5d7a33da33b
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < 75eec935444db4af2123e0491936f6e273d7ea00
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < 384b4dae14277d369221d187e9b3af56c79d2e50
- affected>= f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e and < e0ba936287dfe9783426aac27e5fd76fe35b38c9
- 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.