Linux Kernel: security vulnerability (CVE-2026-80875)
Published Last modified Sources: Ubuntu, HKCERT, BSI, CVE.org, EUVD
What is affected, what to do
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.
Update Linux Kernel to version 5.10.261, Linux Kernel to version 5.15.212, Linux Kernel to version 6.1.178.
- Affected
- Linux Kernel
lt 2.6.28..5.10.261 - Linux Kernel
lt 5.11..5.15.212 - Linux Kernel
lt 5.16..6.1.178 - Linux Kernel
lt 6.2..6.6.145 - Linux Kernel
lt 6.7..6.12.97 - Linux Kernel
lt 6.13..6.18.40 - Linux Kernel
lt 6.19..7.1.5
- Linux Kernel
- Fixed in
- Linux Kernel
5.10.261 - Linux Kernel
5.15.212 - Linux Kernel
6.1.178 - Linux Kernel
6.6.145 - Linux Kernel
6.12.97 - Linux Kernel
6.18.40 - Linux Kernel
7.1.5 - Linux Kernel
7.2
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
—
XIEM Effective CVSS
No value is available for this vulnerability.
0.0
CVSS v3
Severity Not rated on the scale from 0 to 10.
Source: Ubuntu, HKCERT, BSI, CVE.org, EUVD
0.2 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 12.6
Show all metrics
- Severity
- Not rated
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 25.13 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 0.0
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.2 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 12.6
- Elevated — this CVE ranks above at least 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 6 November 2026
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: Ubuntu Security Notices, HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, BSI WID Portal, BSI CSAF, cvelistv5, ENISA EUVD, NVD (NIST), CVE.org (MITRE)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
| Red Hat | OpenShift |
|
|
Vendors and products
Affected operating systems
| Linux | ubuntu | linux | noble |
| Linux | ubuntu | linux | resolute |
| Linux | ubuntu | linux-aws | noble |
| Linux | ubuntu | linux-aws | resolute |
| Linux | ubuntu | linux-aws-6.8 | jammy |
| Linux | ubuntu | linux-aws-7.0 | noble |
| Linux | ubuntu | linux-aws-fips | noble |
| Linux | ubuntu | linux-azure | noble |
| Linux | ubuntu | linux-azure | resolute |
| Linux | ubuntu | linux-azure-6.8 | jammy |
| Linux | ubuntu | linux-azure-7.0 | noble |
| Linux | ubuntu | linux-azure-fde | noble |
| Linux | ubuntu | linux-azure-fde | resolute |
| Linux | ubuntu | linux-azure-fde-6.8 | jammy |
| Linux | ubuntu | linux-azure-fde-7.0 | noble |
| Linux | ubuntu | linux-azure-fips | noble |
| Linux | ubuntu | linux-fips | noble |
| Linux | ubuntu | linux-gcp | noble |
| Linux | ubuntu | linux-gcp | resolute |
| Linux | ubuntu | linux-gcp-6.8 | jammy |
| Linux | ubuntu | linux-gcp-7.0 | noble |
| Linux | ubuntu | linux-gcp-fips | noble |
| Linux | ubuntu | linux-gke | noble |
| Linux | ubuntu | linux-gke | resolute |
References & sources
- git.kernel.orgstable/c/2d06e0897ce18228d199887f0823b431d841dd03euvd
- git.kernel.orgstable/c/816efb7fc0aeae986e63ac73b428dd97a4ef69f5euvd
- git.kernel.orgstable/c/5848e914b85e360a2dd9d19c00a72e2ea9617dd0euvd
- git.kernel.orgstable/c/d45f73c274435703e8d7bc9d8b742a5d9111ab6eeuvd
- git.kernel.orgstable/c/f6f550f26562d191c30b2818e7925dcb1c7f166ceuvd
- git.kernel.orgstable/c/d73f4249776dd970ad65a69cfc51613dd8a034bbeuvd
- git.kernel.orgstable/c/c2ee845e292c278fac75bf28d96bc892607fd5c4euvd
- git.kernel.orgstable/c/2500fa3958b1ba51c2b065e39db1b04dfa7e23a2euvd
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-80875","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-11-06T17:04:00.127070Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedLinux
Description added or changed
New references:- https://git.kernel.org/stable/c/2500fa3958b1ba51c2b065e39db1b04dfa7e23a2
- https://git.kernel.org/stable/c/2d06e0897ce18228d199887f0823b431d841dd03
- https://git.kernel.org/stable/c/5848e914b85e360a2dd9d19c00a72e2ea9617dd0
- https://git.kernel.org/stable/c/816efb7fc0aeae986e63ac73b428dd97a4ef69f5
and 4 more references
Show 10 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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 versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80875.json">CVE-2026-80875</a>Reference added —https://git.kernel.org/stable/c/2500fa3958b1ba51c2b065e39db1b04dfa7e23a2Reference added —https://git.kernel.org/stable/c/2d06e0897ce18228d199887f0823b431d841dd03Reference added —https://git.kernel.org/stable/c/5848e914b85e360a2dd9d19c00a72e2ea9617dd0Reference added —https://git.kernel.org/stable/c/816efb7fc0aeae986e63ac73b428dd97a4ef69f5Reference added —https://git.kernel.org/stable/c/c2ee845e292c278fac75bf28d96bc892607fd5c4Reference added —https://git.kernel.org/stable/c/d45f73c274435703e8d7bc9d8b742a5d9111ab6eReference added —https://git.kernel.org/stable/c/d73f4249776dd970ad65a69cfc51613dd8a034bbReference added —https://git.kernel.org/stable/c/f6f550f26562d191c30b2818e7925dcb1c7f166cSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-80875"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-80875.svg?lang=en" alt="CVE-2026-80875 – NEOSEC Intel" height="20"></a>