Answer in brief
CVE-2026-72021 records a Unknown severity vulnerability in ipvs: use parsed transport offset in SCTP state lookup. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-72021 records a Unknown severity vulnerability in ipvs: use parsed transport offset in SCTP state lookup. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2906f66a5682e5670a5eefe991843689b8d8563f <d2b8b1557ec07ea1bb5dddbceaf4dfe63d388e27 || >=2906f66a5682e5670a5eefe991843689b8d8563f <9f94573ab962a9e81954b755da016fa3cd2f5039 || >=2906f66a5682e5670a5eefe991843689b8d8563f <290e9e8389b556efc603522e28bd1543846aa336 || >=2906f66a5682e5670a5eefe991843689b8d8563f <9cb5ac594ca76d3a71803b23b74c835b0721e628 || >=2906f66a5682e5670a5eefe991843689b8d8563f <a4a2d2e483d79cc2ad3a170674cf159644acf22b || >=2906f66a5682e5670a5eefe991843689b8d8563f <247d055504dcc852e539b9f7f30d19f9741474bf || >=2906f66a5682e5670a5eefe991843689b8d8563f <e5d0bb8871668f20de8f3c94b5ae3f372346bc6e || >=2906f66a5682e5670a5eefe991843689b8d8563f <2f75c0faa3361b28e36cc0512b3299e163e25789 | d2b8b1557ec07ea1bb5dddbceaf4dfe63d388e27, 9f94573ab962a9e81954b755da016fa3cd2f5039, 290e9e8389b556efc603522e28bd1543846aa336, 9cb5ac594ca76d3a71803b23b74c835b0721e628, a4a2d2e483d79cc2ad3a170674cf159644acf22b, 247d055504dcc852e539b9f7f30d19f9741474bf, e5d0bb8871668f20de8f3c94b5ae3f372346bc6e, 2f75c0faa3361b28e36cc0512b3299e163e25789 |
| Linux/Linuxgeneric | 2.6.34 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2906f66a5682e5670a5eefe991843689b8d8563f <d2b8b1557ec07ea1bb5dddbceaf4dfe63d388e27 || >=2906f66a5682e5670a5eefe991843689b8d8563f <9f94573ab962a9e81954b755da016fa3cd2f5039 || >=2906f66a5682e5670a5eefe991843689b8d8563f <290e9e8389b556efc603522e28bd1543846aa336 || >=2906f66a5682e5670a5eefe991843689b8d8563f <9cb5ac594ca76d3a71803b23b74c835b0721e628 || >=2906f66a5682e5670a5eefe991843689b8d8563f <a4a2d2e483d79cc2ad3a170674cf159644acf22b || >=2906f66a5682e5670a5eefe991843689b8d8563f <247d055504dcc852e539b9f7f30d19f9741474bf || >=2906f66a5682e5670a5eefe991843689b8d8563f <e5d0bb8871668f20de8f3c94b5ae3f372346bc6e || >=2906f66a5682e5670a5eefe991843689b8d8563f <2f75c0faa3361b28e36cc0512b3299e163e25789 | d2b8b1557ec07ea1bb5dddbceaf4dfe63d388e27, 9f94573ab962a9e81954b755da016fa3cd2f5039, 290e9e8389b556efc603522e28bd1543846aa336, 9cb5ac594ca76d3a71803b23b74c835b0721e628, a4a2d2e483d79cc2ad3a170674cf159644acf22b, 247d055504dcc852e539b9f7f30d19f9741474bf, e5d0bb8871668f20de8f3c94b5ae3f372346bc6e, 2f75c0faa3361b28e36cc0512b3299e163e25789 |
| Linux/Linuxgeneric | 2.6.34 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.