Linux Kernel: security vulnerability (CVE-2026-80862)
Published Last modified Sources: HKCERT, Ubuntu, Debian LTS, Debian, SUSE, BSI, CVE.org, EUVD
What is affected, what to do
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix usage of page_frag_cache nvme uses page_frag_cache to preallocate PDU for each preallocated request of block device. Block devices are created in parallel threads, consequently page_frag_cache is used in not thread-safe manner.
Update Linux Kernel to version 6.7, Linux Kernel to version 6.12.108, Linux Kernel to version 6.18.49.
- Affected
- Linux Kernel
lt 6.6.160..6.7 - Linux Kernel
lt 6.12..6.12.108 - Linux Kernel
lt 6.13..6.18.49 - Linux Kernel
lt 6.19..7.1.13 - Linux Kernel
lt 7.2..7.2.3
- Linux Kernel
- Fixed in
- Linux Kernel
6.7 - Linux Kernel
6.12.108 - Linux Kernel
6.18.49 - Linux Kernel
7.1.13 - Linux Kernel
7.2.3 - Linux Kernel
7.3
- 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: HKCERT, Ubuntu, Debian LTS, Debian, SUSE, BSI, CVE.org, EUVD
0.2 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 4.9
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- 24.26 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- 4.9
- Low — this CVE sits in the lower 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
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: nvme-tcp: fix usage of page_frag_cache nvme uses page_frag_cache to preallocate PDU for each preallocated request of block device. Block devices are created in parallel threads, consequently page_frag_cache is used in not thread-safe manner. That leads to incorrect refcounting of backstore pages and premature free. That can be catched by !sendpage_ok inside network stack: WARNING: CPU: 7 PID: 467 at ../net/core/skbuff.c:6931 skb_splice_from_iter+0xfa/0x310. tcp_sendmsg_locked+0x782/0xce0 tcp_sendmsg+0x27/0x40 sock_sendmsg+0x8b/0xa0 nvme_tcp_try_send_cmd_pdu+0x149/0x2a0 Then random panic may occur. Fix that by serializing the usage of page_frag_cache.
Source: HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Ubuntu Security Notices, Debian LTS Advisories, Debian Security Advisories, suse_csaf, BSI WID Portal, BSI CSAF, NVD (NIST), cvelistv5, CVE.org (MITRE), ENISA EUVD
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 | debian | linux | trixie |
| Linux | ubuntu | linux | resolute |
| Linux | debian | linux-6.12 | bookworm |
| Linux | ubuntu | linux-aws | resolute |
| Linux | ubuntu | linux-aws-7.0 | noble |
| Linux | ubuntu | linux-azure | resolute |
| Linux | ubuntu | linux-azure-fde | resolute |
| Linux | ubuntu | linux-azure-fde-7.0 | noble |
| Linux | ubuntu | linux-gcp | resolute |
| Linux | ubuntu | linux-gcp-7.0 | noble |
| Linux | ubuntu | linux-gke | resolute |
| Linux | ubuntu | linux-hwe-7.0 | noble |
| Linux | ubuntu | linux-ibm | resolute |
| Linux | ubuntu | linux-oem-7.0 | resolute |
| Linux | ubuntu | linux-oracle | resolute |
| Linux | ubuntu | linux-oracle-7.0 | noble |
| Linux | ubuntu | linux-realtime | resolute |
References & sources
- git.kernel.orgstable/c/d19f98c79f1b7e09e4cdf5c20d626e571e487467euvd
- git.kernel.orgstable/c/64561afb42d8390695bf810d9bbd087cbca00291euvd
- git.kernel.orgstable/c/0a9750263ffacbbd2048a391fd4bd22e2146c57deuvd
- git.kernel.orgstable/c/6e4cf281558709b92ec2ca3054fe2ffc69266ef9euvd
- git.kernel.orgstable/c/36ac05f7cfd59d90c597071304b14e98090d5dd1euvd
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 modifiedLinux
1 individual change: Affected versions (publisher)
Show the original change
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80862.json">CVE-2026-80862</a>Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedLinux
1 individual change: Affected versions (publisher)
Show the original change
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80862.json">CVE-2026-80862</a>Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
ReceivedLinux
Description added or changed
New references:- https://git.kernel.org/stable/c/0a9750263ffacbbd2048a391fd4bd22e2146c57d
- https://git.kernel.org/stable/c/36ac05f7cfd59d90c597071304b14e98090d5dd1
- https://git.kernel.org/stable/c/64561afb42d8390695bf810d9bbd087cbca00291
- https://git.kernel.org/stable/c/6e4cf281558709b92ec2ca3054fe2ffc69266ef9
and 1 more reference
Show 7 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: nvme-tcp: fix usage of page_frag_cache nvme uses page_frag_cache to preallocate PDU for each preallocated request of block device. Block devices are created in parallel threads, consequently page_frag_cache is used in not thread-safe manner. That leads to incorrect refcounting of backstore pages and premature free. That can be catched by !sendpage_ok inside network stack: WARNING: CPU: 7 PID: 467 at ../net/core/skbuff.c:6931 skb_splice_from_iter+0xfa/0x310. tcp_sendmsg_locked+0x782/0xce0 tcp_sendmsg+0x27/0x40 sock_sendmsg+0x8b/0xa0 nvme_tcp_try_send_cmd_pdu+0x149/0x2a0 Then random panic may occur. Fix that by serializing the usage of page_frag_cache.Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80862.json">CVE-2026-80862</a>Reference added —https://git.kernel.org/stable/c/0a9750263ffacbbd2048a391fd4bd22e2146c57dReference added —https://git.kernel.org/stable/c/36ac05f7cfd59d90c597071304b14e98090d5dd1Reference added —https://git.kernel.org/stable/c/64561afb42d8390695bf810d9bbd087cbca00291Reference added —https://git.kernel.org/stable/c/6e4cf281558709b92ec2ca3054fe2ffc69266ef9Reference added —https://git.kernel.org/stable/c/d19f98c79f1b7e09e4cdf5c20d626e571e487467Source 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-80862"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-80862.svg?lang=en" alt="CVE-2026-80862 – NEOSEC Intel" height="20"></a>