CVE-2026-72021

ipvs: use parsed transport offset in SCTP state lookup

HIGH
8.2
CVSS Score
Published: August 15, 2026 at 05:51 AM UTC
Updated: October 19, 2026 at 10:17 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
HIGH8.2
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: ipvs: use parsed transport offset in SCTP state lookup set_sctp_state() reads the SCTP chunk header again in order to drive the IPVS SCTP state table. For IPv6 it computes the offset with sizeof(struct ipv6hdr), while the surrounding IPVS code uses iph.len from ip_vs_fill_iph_skb(), where ipv6_find_hdr() has already skipped extension headers and found the real transport header. This makes the state machine read from the wrong offset for IPv6 SCTP packets that carry extension headers. For example, an INIT packet with an 8-byte destination options header can be scheduled correctly by sctp_conn_schedule(), but set_sctp_state() reads the first byte of the SCTP verification tag as a DATA chunk type. The connection then moves from NONE to ESTABLISHED instead of INIT1, gets the longer established timeout, and updates the active/inactive destination counters incorrectly. This happens even though the SCTP handshake has not completed. Use the parsed transport offset passed down from ip_vs_set_state() for the SCTP chunk-header lookup. For IPv4 and IPv6 packets without extension headers this preserves the existing offset.

Affected

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

2.6.342906f66a5682e5670a5eefe991843689b8d8563f
Vendor states this is fixed in 247d055504dcc852e539b9f7f30d19f9741474bf (fixed)
Vendor states this is fixed in 290e9e8389b556efc603522e28bd1543846aa336 (fixed)
Vendor states this is fixed in 2f75c0faa3361b28e36cc0512b3299e163e25789 (fixed)
Vendor states this is fixed in 9cb5ac594ca76d3a71803b23b74c835b0721e628 (fixed)
Vendor states this is fixed in 9f94573ab962a9e81954b755da016fa3cd2f5039 (fixed)
Vendor states this is fixed in a4a2d2e483d79cc2ad3a170674cf159644acf22b (fixed)
Vendor states this is fixed in d2b8b1557ec07ea1bb5dddbceaf4dfe63d388e27 (fixed)
Vendor states this is fixed in e5d0bb8871668f20de8f3c94b5ae3f372346bc6e (fixed)
Vendor states this is fixed in 2.6.34 (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.

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.2HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-20

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