CVE-2026-95702
Description
A flaw was found in Google gVisor's Virtual File System (VFS). A local attacker with standard container privileges can exploit this vulnerability to achieve arbitrary code execution within the host sentry process. By improperly releasing a backing memory file multiple times from an in-sandbox overlay filesystem, the attacker triggers a use-after-free memory corruption condition. While code execution occurs in the sentry process, the process remains restricted by host-level security filters and namespace boundaries.
Statement
A use-after-free vulnerability in Google gVisor's Virtual File System (VFS) allows a local attacker with standard container privileges inside a gVisor sandbox to trigger a double-free of the backing MemoryFile of an in-sandbox overlay filesystem, causing memory corruption and arbitrary code execution within the host sentry process. The sentry process remains confined by host-level Linux seccomp filters and namespace boundaries, so code execution does not directly translate into escape to the wider host. Red Hat evaluates this flaw as IMPORTANT severity (CVSS 3.1 score 7.8); the CVEORG record assigns a CVSS 4.0 score of 8.5 (also IMPORTANT), a difference attributable to the scoring methodology rather than a material difference in severity.
No Red Hat-maintained component is listed as affected. The components that vendor portions of the gVisor source -- gvisor-tap-vsock and podman in Red Hat Enterprise Linux, Red Hat In-Vehicle OS, and OpenShift Container Platform, as well as Fedora community packages such as rootlesskit, headscale, spoofdpi, nebula, and tailscale -- are all recorded as NOT AFFECTED because the vulnerable VFS overlay/MemoryFile code is not present in those builds; these components consume only parts of the gVisor library rather than the gVisor sandbox runtime itself.
Mitigation
Mitigation for this issue is either not available or the currently available options do not 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.8 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | High | N/A | N/A |
| Integrity Impact | High | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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.