CVE-2026-80875

ipvs: use parsed transport offset in TCP state lookup

N/A
Published: September 4, 2026 at 04:48 PM UTC
Updated: September 4, 2026 at 05: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: 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.

Affected

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

2.6.28 ≤ v < 5.10.2612.6.28 ≤ v < 5.15.2122.6.28 ≤ v < 6.1.1782.6.28 ≤ v < 6.12.972.6.28 ≤ v < 6.18.402.6.28 ≤ v < 6.6.1452.6.28 ≤ v < 7.1.52.6.28 ≤ v < 7.20bbdd42b7efa66685b6d74701bcde3a596a3a59d2.6.28
Vendor states this is fixed in 2500fa3958b1ba51c2b065e39db1b04dfa7e23a2 (fixed)
Vendor states this is fixed in 2d06e0897ce18228d199887f0823b431d841dd03 (fixed)
Vendor states this is fixed in 5848e914b85e360a2dd9d19c00a72e2ea9617dd0 (fixed)
Vendor states this is fixed in 816efb7fc0aeae986e63ac73b428dd97a4ef69f5 (fixed)
Vendor states this is fixed in c2ee845e292c278fac75bf28d96bc892607fd5c4 (fixed)
Vendor states this is fixed in d45f73c274435703e8d7bc9d8b742a5d9111ab6e (fixed)
Vendor states this is fixed in d73f4249776dd970ad65a69cfc51613dd8a034bb (fixed)
Vendor states this is fixed in f6f550f26562d191c30b2818e7925dcb1c7f166c (fixed)
Vendor states this is fixed in 2.6.28 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (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