ipvs: fix the checksum validations
Summary
| CVE | CVE-2026-80901 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-04 18:17:58 UTC |
| Updated | 2026-09-04 18:17:58 UTC |
| 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. |
Risk And Classification
EPSS: 0.001610000 probability, percentile 0.055690000 (date 2026-09-07)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 2a3b791e6e1169f374224d164738e9f7be703d77 d418d73acf8be62744dc47359dfdde8c2148845d git | Not specified |
| CNA | Linux | Linux | affected 2a3b791e6e1169f374224d164738e9f7be703d77 b3869d9b54e76dff64118dee4c8fd9302fcd5171 git | Not specified |
| CNA | Linux | Linux | affected 2a3b791e6e1169f374224d164738e9f7be703d77 9cbe2c0fdb71904ee929b1851cdc1c73341a03c0 git | Not specified |
| CNA | Linux | Linux | affected 2a3b791e6e1169f374224d164738e9f7be703d77 00eb23829fd08df1b5e057cb6b625996a70e7e65 git | Not specified |
| CNA | Linux | Linux | affected 2a3b791e6e1169f374224d164738e9f7be703d77 5558a85add073215b298f3e044ff9a6d86d714ae git | Not specified |
| CNA | Linux | Linux | affected 2a3b791e6e1169f374224d164738e9f7be703d77 e876b75b9020a97bbdc79721e7fc749024891c65 git | Not specified |
| CNA | Linux | Linux | affected 2.6.28 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.28 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.183 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.151 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.103 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.44 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.8 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/00eb23829fd08df1b5e057cb6b625996a70e7e65 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/5558a85add073215b298f3e044ff9a6d86d714ae | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/9cbe2c0fdb71904ee929b1851cdc1c73341a03c0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/d418d73acf8be62744dc47359dfdde8c2148845d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e876b75b9020a97bbdc79721e7fc749024891c65 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b3869d9b54e76dff64118dee4c8fd9302fcd5171 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.