CVE-2026-80862

Description

A flaw was found in the Linux kernel's nvme-tcp component. When block devices are created in parallel threads, the page_frag_cache is used in a manner that is not thread-safe. This can lead to incorrect reference counting of memory pages and premature freeing, potentially causing a system crash (Denial of Service).

Statement

A race in the NVMe TCP host path can occur because page_frag_cache is used without serialization while block devices and preallocated requests are initialized in parallel. This can corrupt page reference accounting for PDU backing pages and may cause premature free, followed by warnings in skb_splice_from_iter and random kernel panic. For the CVSS the PR:N is used for the paranoid score because a malicious or compromised NVMe TCP target may influence namespace discovery and request initialization without local code execution on the victim. The issue is best treated as adjacent network reachable in storage fabric deployments rather than a public Internet bug. Impact is at least denial of service via kernel crash and in worst case may allow confidentiality or integrity impact due to memory lifetime corruption and should be reviewed manually.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.1N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.