CVE-2026-80901 — ipvs: fix the checksum validations
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ 2a3b791e6e1169f374224d164738e9f7be703d77 and < d418d73acf8be62744dc47359dfdde8c2148845d≥ 2a3b791e6e1169f374224d164738e9f7be703d77 and < b3869d9b54e76dff64118dee4c8fd9302fcd5171≥ 2a3b791e6e1169f374224d164738e9f7be703d77 and < 9cbe2c0fdb71904ee929b1851cdc1c73341a03c0≥ 2a3b791e6e1169f374224d164738e9f7be703d77 and < 00eb23829fd08df1b5e057cb6b625996a70e7e65≥ 2a3b791e6e1169f374224d164738e9f7be703d77 and < 5558a85add073215b298f3e044ff9a6d86d714ae≥ 2a3b791e6e1169f374224d164738e9f7be703d77 and < e876b75b9020a97bbdc79721e7fc749024891c65version 2.6.28 | Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 26, 2026 · 11 reading(s) · max 0.16%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
6 on the record
- git.kernel.org/stable/c/d418d73acf8be62744dc47359dfdde8c2148845d
- git.kernel.org/stable/c/e876b75b9020a97bbdc79721e7fc749024891c65
- git.kernel.org/stable/c/5558a85add073215b298f3e044ff9a6d86d714ae
- git.kernel.org/stable/c/9cbe2c0fdb71904ee929b1851cdc1c73341a03c0
- git.kernel.org/stable/c/00eb23829fd08df1b5e057cb6b625996a70e7e65
- git.kernel.org/stable/c/b3869d9b54e76dff64118dee4c8fd9302fcd5171
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 16h
- Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 16h
- Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 16h
- Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 16h
- Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 16h
- Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 16h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80901 is "ipvs: fix the checksum validations", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.16% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.