GHSA-X476-X69X-M4JR
Vulnerability from github – Published: 2026-09-04 18:31 – Updated: 2026-09-04 18:31In 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": [],
"aliases": [
"CVE-2026-80875"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-04T17:16:59Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nipvs: use parsed transport offset in TCP state lookup\n\nTCP state handling reparses the skb to find the TCP header. For IPv6 it\nuses sizeof(struct ipv6hdr), while the surrounding IPVS code already\nparsed the packet with ip_vs_fill_iph_skb() and has the real\ntransport-header offset in iph.len.\n\nThis makes TCP state handling look at the wrong bytes when an IPv6\npacket carries extension headers. Use the parsed transport offset passed\ndown from ip_vs_set_state() when reading the TCP header.\n\nFor IPv4 and for IPv6 packets without extension headers, the passed\noffset matches the previous value.",
"id": "GHSA-x476-x69x-m4jr",
"modified": "2026-09-04T18:31:32Z",
"published": "2026-09-04T18:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80875"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2500fa3958b1ba51c2b065e39db1b04dfa7e23a2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2d06e0897ce18228d199887f0823b431d841dd03"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5848e914b85e360a2dd9d19c00a72e2ea9617dd0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/816efb7fc0aeae986e63ac73b428dd97a4ef69f5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c2ee845e292c278fac75bf28d96bc892607fd5c4"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d45f73c274435703e8d7bc9d8b742a5d9111ab6e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d73f4249776dd970ad65a69cfc51613dd8a034bb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f6f550f26562d191c30b2818e7925dcb1c7f166c"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.