CVE-2026-72021

CVE CVE-2026-72021EUVD EUVD-2026-58979Published 2026-08-15T05:51:47.000ZLast changed 2026-08-17T05:39:31.000ZCVSS 8.2

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 2906f66a5682e5670a5eefe991843689b8d8563f <2f75c0faa3361b28e36cc0512b3299e163e25789; patch: 5.15.212; 2.6.34; 2906f66a5682e5670a5eefe991843689b8d8563f <9f94573ab962a9e81954b755da016fa3cd2f5039; 2906f66a5682e5670a5eefe991843689b8d8563f <a4a2d2e483d79cc2ad3a170674cf159644acf22b; patch: 7.2; patch: 6.12.97; patch: 6.6.145; 2906f66a5682e5670a5eefe991843689b8d8563f <d2b8b1557ec07ea1bb5dddbceaf4dfe63d388e27; 2906f66a5682e5670a5eefe991843689b8d8563f <9cb5ac594ca76d3a71803b23b74c835b0721e628; patch: 6.18.40; patch: 0; patch: 6.1.178; 2906f66a5682e5670a5eefe991843689b8d8563f <247d055504dcc852e539b9f7f30d19f9741474bf; 2906f66a5682e5670a5eefe991843689b8d8563f <290e9e8389b556efc603522e28bd1543846aa336; patch: 7.1.5; 2906f66a5682e5670a5eefe991843689b8d8563f <e5d0bb8871668f20de8f3c94b5ae3f372346bc6e; patch: 5.10.261

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.