GPU Firmware vulnerabilities

Kernel software running inside a Guest VM may post improper commands to the GPU Firmware to trigger a write of data outside the Guest's virtualised GPU memory. This can result in out of bounds memory accesses and be used to escalate privileges.

Kernel software from a non-secure operating system on a platform with Trusted Execution Environment support may cause GPU Firmware to boot up using data from non-secure memory. The GPU thread of control (Firmware) uses a pointer from non-secure memory belonging to the Rich Execution Environment (REE) when saving or retrieving internal data between the tightly coupled private memory to main memory. An attacker with control over the REE kernel may modify the pointer value, corrupting the data used by the GPU Firmware.

A vulnerability in kernel software running inside a Host VM allows sending improper commands to GPU firmware, leading to unauthorized GPU register access and privilege escalation.

A vulnerability in kernel software running inside a Host VM allows sending improper commands to the GPU firmware, potentially causing memory read or write outside the permitted range. Addresses passed to the GPU firmware can be used to gain more privileged memory access than allowed by the system.

Kernel software in a Guest/Host VM may send improper commands to GPU firmware, causing out-of-bounds writes. A logic error in address translation allows a compromised Host (Kernel) to perform arbitrary writes to firmware memory.