Use-after-free in Google gVisor VFS before 20260831.0 (double-free MemoryFile)
CVE-2026-95702 Published on October 9, 2026

Code Execution in Host Sentry Process via Double Free in gVisor VFS MemoryFile
Use-after-free vulnerability in VFS in Google gVisor prior to release 20260831.0 on all platforms allows a local attacker with standard container privileges to achieve code execution in the host sentry process by double-freeing the backing MemoryFile from an in-sandbox overlay filesystem. The sentry process remains confined by host-level Linux seccomp and namespace boundaries.

NVD

Vulnerability Analysis

CVE-2026-95702 is exploitable with local system access, and requires small amount of user privileges. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity and availability.

Attack Vector:
LOCAL
Attack Complexity:
LOW
Privileges Required:
LOW
User Interaction:
NONE

Weakness Types

What is a Dangling pointer Vulnerability?

Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.

CVE-2026-95702 has been classified to as a Dangling pointer vulnerability or weakness.

What is a Double-free Vulnerability?

The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations. When a program calls free() twice with the same argument, the program's memory management data structures become corrupted. This corruption can cause the program to crash or, in some circumstances, cause two later calls to malloc() to return the same pointer. If malloc() returns the same value twice and the program later gives the attacker control over the data that is written into this doubly-allocated memory, the program becomes vulnerable to a buffer overflow attack.

CVE-2026-95702 has been classified to as a Double-free vulnerability or weakness.


Products Associated with CVE-2026-95702

Want to know whenever a new CVE is published for Google Gvisor? stack.watch will email you.

 

Affected Versions

Google gVisor: