CVE-2026-80901

ipvs: fix the checksum validations

N/A
Published: September 4, 2026 at 05:11 PM UTC
Updated: September 4, 2026 at 06:36 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ipvs: fix the checksum validations ip_vs_in_icmp_v6() is missing checksum validation for ICMPv6 packets from clients. In fact, as for TCP/UDP we should validate the checksum for ICMP packets only when we mangle the packets on MASQ or on reply for tunnel. Also, Sashiko points out that handle_response_icmp() being common for IPv4 and IPv6 is missing the pseudo-header calculation while validating ICMPv6 messages from real servers which is a problem if checksum is not validated by the hardware. Fix the problems by creating ip_vs_checksum_common_check() helper and use it for TCP/UDP/ICMP both for IPv4 and IPv6. Rely on the nf_checksum() for validating the ICMP messages but use it also for TCP and UDP. Use correct IP offset for IP_VS_DBG_RL_PKT for TCP/UDP/SCTP. IPVS packets (TCP/UDP/SCTP/ICMP) do not need checksum validation on LOCAL_OUT (local clients or local real servers) and on FORWARD (traffic from servers on LAN). Do it only on LOCAL_IN, in case nf_checksum() is not called on PRE_ROUTING. Also, ip_vs_checksum_complete() can be marked static.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.28 ≤ v < 6.1.1832.6.28 ≤ v < 6.12.1032.6.28 ≤ v < 6.18.442.6.28 ≤ v < 6.6.1512.6.28 ≤ v < 7.1.82.6.28 ≤ v < 7.22.6.282a3b791e6e1169f374224d164738e9f7be703d77
Vendor states this is fixed in 00eb23829fd08df1b5e057cb6b625996a70e7e65 (fixed)
Vendor states this is fixed in 5558a85add073215b298f3e044ff9a6d86d714ae (fixed)
Vendor states this is fixed in 9cbe2c0fdb71904ee929b1851cdc1c73341a03c0 (fixed)
Vendor states this is fixed in b3869d9b54e76dff64118dee4c8fd9302fcd5171 (fixed)
Vendor states this is fixed in d418d73acf8be62744dc47359dfdde8c2148845d (fixed)
Vendor states this is fixed in e876b75b9020a97bbdc79721e7fc749024891c65 (fixed)
Vendor states this is fixed in 2.6.28 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card