CVE-2026-80875ipvs: use parsed transport offset in TCP state lookup
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ipvs: use parsed transport offset in TCP state lookup TCP state handling reparses the skb to find the TCP header. For IPv6 it uses sizeof(struct ipv6hdr), while the surrounding IPVS code already parsed the packet with ip_vs_fill_iph_skb() and has the real transport-header offset in iph.len. This makes TCP state handling look at the wrong bytes when an IPv6 packet carries extension headers. Use the parsed transport offset passed down from ip_vs_set_state() when reading the TCP header. For IPv4 and for IPv6 packets without extension headers, the passed offset matches the previous value.
Timeline
ID reserved
By Linux
- 9 days later
· 9 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 0bbdd42b7efa66685b6d74701bcde3a596a3a59d – < 2d06e0897ce18228d199887f0823b431d841dd03
- affected 0bbdd42b7efa66685b6d74701bcde3a596a3a59d – < 816efb7fc0aeae986e63ac73b428dd97a4ef69f5
- affected 0bbdd42b7efa66685b6d74701bcde3a596a3a59d – < 5848e914b85e360a2dd9d19c00a72e2ea9617dd0
- affected 0bbdd42b7efa66685b6d74701bcde3a596a3a59d – < d45f73c274435703e8d7bc9d8b742a5d9111ab6e
- affected 0bbdd42b7efa66685b6d74701bcde3a596a3a59d – < f6f550f26562d191c30b2818e7925dcb1c7f166c
- affected 0bbdd42b7efa66685b6d74701bcde3a596a3a59d – < d73f4249776dd970ad65a69cfc51613dd8a034bb
- affected 0bbdd42b7efa66685b6d74701bcde3a596a3a59d – < c2ee845e292c278fac75bf28d96bc892607fd5c4
- affected 0bbdd42b7efa66685b6d74701bcde3a596a3a59d – < 2500fa3958b1ba51c2b065e39db1b04dfa7e23a2
- affected 2.6.28
- unaffected < 2.6.28
- unaffected 5.10.261 – ≤ 5.10.*
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/2d06e0897ce18228d199887f0823b431d841dd03 (opens in a new tab)
- https://git.kernel.org/stable/c/816efb7fc0aeae986e63ac73b428dd97a4ef69f5 (opens in a new tab)
- https://git.kernel.org/stable/c/5848e914b85e360a2dd9d19c00a72e2ea9617dd0 (opens in a new tab)
- https://git.kernel.org/stable/c/d45f73c274435703e8d7bc9d8b742a5d9111ab6e (opens in a new tab)
- https://git.kernel.org/stable/c/f6f550f26562d191c30b2818e7925dcb1c7f166c (opens in a new tab)
- https://git.kernel.org/stable/c/d73f4249776dd970ad65a69cfc51613dd8a034bb (opens in a new tab)
- https://git.kernel.org/stable/c/c2ee845e292c278fac75bf28d96bc892607fd5c4 (opens in a new tab)
- https://git.kernel.org/stable/c/2500fa3958b1ba51c2b065e39db1b04dfa7e23a2 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-71505 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80875)Record last updated .