CVE-2026-63917
Description
A flaw was found in the Linux kernel's IPv6 Virtual Tunnel Interface (vti6) component. An unprivileged local user, particularly within a user namespace, could exploit a vulnerability related to incorrect network namespace handling during the movement of a vti6 tunnel. This issue can lead to a kernel bug, resulting in a denial of service (system crash) and potentially impacting container isolation on affected hosts.
Statement
A stale per-network-namespace VTI6 tunnel entry can remain after a VTI6 device is moved between network namespaces because the update and changelink paths use the device's current network namespace instead of the tunnel's original namespace. When the original namespace is later destroyed, cleanup_net() may access the stale entry after the associated object has been freed, resulting in a use-after-free condition.
The vulnerability is considered to require low privileges (PR:L) because an unprivileged local user can reach the affected code path by creating user and network namespaces and obtaining the required capabilities within the newly created user namespace, where unprivileged user namespaces are enabled. Host-level CAP_NET_ADMIN is therefore not required. The issue is not remotely exploitable through network traffic; exploitation requires local netlink and network-namespace operations.
Successful exploitation can cause a kernel crash and host-wide denial of service. Because the underlying flaw is a kernel use-after-free, confidentiality and integrity impacts may also be possible, although privilege escalation has not been demonstrated. The practical impact can be greater on container hosts because an unprivileged workload with access to user and network namespaces may trigger the flaw in the shared host kernel, potentially affecting other containers or tenants outside the attacker's own namespace.
Mitigation
To mitigate this issue, prevent module ip6_vti from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically.
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).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7 | N/A | 8.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 | Changed |
| 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:C/C:H/I:H/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.