Kernel-level IPVS bug affects widely deployed Linux networking/load-balancing (kube-proxy IPVS, IPVS LBs), with potential for widespread service disruption and evasion.
CVE-2026-68477
Linux kernel IPVS IPv6 transport-offset bug may mishandle IPv6 packets
Is CVE-2026-68477 being exploited?
Not confirmed. CVE-2026-68477 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.71% probability of exploitation in the next 30 days.
How severe is CVE-2026-68477?
CVE-2026-68477 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-68477?
Yes. A fix has been recorded for CVE-2026-68477. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-68477 affect?
CVE-2026-68477 affects Linux kernel (ipvs subsystem), Kubernetes kube-proxy (IPVS mode), IPVS-based load balancers, Distributions shipping affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-68477?
Apply vendor kernel updates/backports for ipvs immediately and restart or reload affected services.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Malformed IPv6 packets (with extension headers) can cause IPVS to mis-parse transport headers, enabling filtering bypass, traffic misrouting, or DoS of services behind IPVS.
Immediate action required
- affected>= 2a3b791e6e1169f374224d164738e9f7be703d77 and < 613ce63711b8d431bba90781f133c39a21684f87
- affected>= 2a3b791e6e1169f374224d164738e9f7be703d77 and < 95d4511d81b2b37e5d2bdde5d912e48243eae517
- affected>= 2a3b791e6e1169f374224d164738e9f7be703d77 and < 3a9dc9b55b53d94613a587604b77d3b20024090c
- affected>= 2a3b791e6e1169f374224d164738e9f7be703d77 and < a3f0d5b605cd5da5c95279969fb8cea4e55cee5b
- affected>= 2a3b791e6e1169f374224d164738e9f7be703d77 and < 7350eb7ead172ae8024897d4b0f2e15c5318279c
- affected>= 2a3b791e6e1169f374224d164738e9f7be703d77 and < d4ec18f48ce78a3bf7c999ac908691007375fe99
- affected>= 2a3b791e6e1169f374224d164738e9f7be703d77 and < 905d7a363ade96a19f214815361e11981142c547
- affected>= 2a3b791e6e1169f374224d164738e9f7be703d77 and < b3fe4cbd583895987935a9bdad01c8f9d3a02310
- affected2.6.28
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.