Affects the Linux kernel IPVS path used broadly (load balancers, kube-proxy ipvs). Remote kernel memory corruption can cause widespread RCE/DoS across servers and cloud infrastructure.
CVE-2026-68476
Linux kernel IPVS memory corruption via skb_ensure_writable reallocation
Is CVE-2026-68476 being exploited?
Not confirmed. CVE-2026-68476 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.69% probability of exploitation in the next 30 days.
How severe is CVE-2026-68476?
CVE-2026-68476 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-68476?
Yes. A fix has been recorded for CVE-2026-68476. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-68476 affect?
CVE-2026-68476 affects Linux kernel (IPVS module), Load balancers using IPVS, Kubernetes kube-proxy (ipvs mode), Cloud VMs and servers running affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-68476?
Apply kernel updates immediately; disable IPVS or block IPVS traffic until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote kernel memory corruption from crafted packets leading to denial-of-service or potential remote code execution and privilege escalation.
Immediate action required
- affected>= 8d8e20e2d7bba8c50e64e0eca1cb83956f468e49 and < 4f2d1151421520d7ae16ca8d367d0ca09f5dfbd7
- affected>= 8d8e20e2d7bba8c50e64e0eca1cb83956f468e49 and < 657118cad620172dfd8f6ed5717fd75c0d1f7a5a
- affected>= 8d8e20e2d7bba8c50e64e0eca1cb83956f468e49 and < a10f5080afbed242640f2984328de25f84557da1
- affected>= 8d8e20e2d7bba8c50e64e0eca1cb83956f468e49 and < ac6ac3d35bfc0ade9d17d354c84e503a946ebdab
- affected>= 8d8e20e2d7bba8c50e64e0eca1cb83956f468e49 and < e51687fc56c2e39ea6e9532925f1aabd4d529f61
- affected>= 8d8e20e2d7bba8c50e64e0eca1cb83956f468e49 and < 3fb7edd2018bb1ad0a68157383d9b9dac33dd645
- affected>= 8d8e20e2d7bba8c50e64e0eca1cb83956f468e49 and < ad1e14710b360bda087ebf9fb82460eb5ef775de
- affected>= 8d8e20e2d7bba8c50e64e0eca1cb83956f468e49 and < a2f57827bf7c695b8c72dc4511cae8e86582369d
- affected4.10
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.