Medium severity · published Dec 17, 2018
CVE-2018-20168
Google gVisor before 2018-08-22 reuses a pagetable in a different level with the paging-structure cache intact, which allows attackers to cause a denial of service ("physical…
5.5
CVSS
0.3%
EPSS
No
On KEV
Description
Google gVisor before 2018-08-22 reuses a pagetable in a different level with the paging-structure cache intact, which allows attackers to cause a denial of service ("physical address not valid" panic) via a crafted application.
CVSS vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 20% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
GV
Gvisor · Google
before 2018-08-22 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2018-20168
CVE.org
https://www.cve.org/CVERecord?id=CVE-2018-20168
Patch
https://bugs.chromium.org/p/project-zero/issues/detail?id=1674
More from Gvisor
9.8
CVE-2018-19333
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…
8.8
CVE-2026-96812
Host Root Sandbox Escape in gVisor via Character Device Passthrough and CUSE
8.5
CVE-2026-95702
Code Execution in Host Sentry Process via Double Free in gVisor VFS MemoryFile
7.8
CVE-2025-2713
Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling of file access permissions, which allowed unprivileged users to…
6.8
CVE-2018-16359
Google gVisor before 2018-08-23, within the seccomp sandbox, permits access to the renameat system call, which allows attackers to rename files on the host OS