The vulnerability arises from improper exposure of host resources in gVisor’s file helper (gofer) when CUSE is enabled. A container that includes a /dev/cuse character device can open it to pass the operation through to the host. An attacker who controls container image deployment can then use the unrestricted ioctl handling of CUSE to register a host device and overwrite memory used by the root udev helper, achieving root code execution on the host system.

Any Linux deployment running Google gVisor before commit 573a9e73cf844f with CUSE enabled is affected. Containers that include a /dev/cuse node and are pushed to the host by users with image deployment privileges are at risk.

The vulnerability carries a CVSS score of 8.8, indicating a high severity level. The exploit requires a local attacker that can push a container image to the host and the host must have CUSE enabled. Because the attacker needs no network exposure and can acquire local container privileges, the potential impact is significant. No EPSS score is available and the flaw is not listed in CISA’s KEV catalog, but the high CVSS and the straightforward local exploitation path make it a priority risk.