CVE-2026-97602
Description
A flaw was found in the Linux kernel. During network namespace cleanup, incomplete packet fragmentation queues are flushed without properly updating their completion state. A local attacker with access to unprivileged network namespaces can exploit this race condition during IPv6 packet reassembly, leading to out-of-bounds memory access and heap corruption. This issue may allow an attacker to achieve local privilege escalation or cause a denial of service (DoS) by crashing the system.
Statement
A race during fqdir teardown can leave an incomplete fragment queue reusable with stale IPv6 reassembly metadata after its skbs have been flushed. A new fragment can then be processed with an old nhoffset, causing a slab out of bounds write and a subsequent out of bounds read next to an skbuff_small_head object. The confirmed heap corruption can cause a kernel crash and may be leveraged for local privilege escalation when unprivileged user and network namespaces are available. For the CVSS the PR:L reflects that a local unprivileged user or process is required to create or control the relevant namespace and fragment traffic, even if namespace capabilities provide access to packet sockets. AC:H is used because reliable triggering depends on winning a race during fqdir teardown. The issue is not considered directly network reachable because reliable exploitation requires local namespace lifecycle control rather than only sending packets from a remote host. Impact is at least a local denial of service via kernel crash and in the worst case may allow high confidentiality and integrity impact through the confirmed heap out of bounds write.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7 | N/A | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.