pkg/sentry/kernel/shm/shm.go in Google gVisor before 2018-11-01 allows attackers to overwrite memory locations in processes running as root (but not escape the sandbox) via vectors involving IPC_RMID shmctl calls, because reference counting is mishandled.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HGoogle Gvisor
APPGoogle< 2018-11-01
Related vulnerabilities
Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling...
A weak hashing algorithm and small sizes of seeds/secrets in Google's gVisor allowed for a remote attacker to ...
Weaknesses in the generation of TCP/UDP source ports and some other header values in Google's gVisor allowed t...
A denial of service exists in Gvisor Sandbox where a bug in reference counting code in mount point tracking co...
Google gVisor before 2018-08-22 reuses a pagetable in a different level with the paging-structure cache intact...