Intel processor graphics blitter command streamer: The graphics blitter accepted commands that could reference memory

Impact

The graphics blitter accepted commands that could reference memory outside the submitting context, letting a local user with GPU access read or write memory belonging to another context. This is the archetype of the GPU isolation failure operators care about: one tenant's GPU commands reaching another tenant's GPU memory. Mitigated by kernel command parsing, which costs measurable submission throughput.

Who can reach it

Any local user or container able to submit GPU work through the DRM interface.

What to do

Take the kernel fix (which re-enables blitter command parsing) plus the Intel graphics firmware/driver update, then reboot. Expect a performance regression on blitter-heavy workloads - that is the mitigation working, not a bug. Kernel + graphics driver, no BIOS.

References

Related entries

• Intel SGX SDK: Insufficient initialisation in the SGX SDK means enclaves built with the affected SDK can leakCVE-2019-14565 · Intel SGX SDKHigh
• Intel SGX SDK: Insufficient input validation in the SGX SDK's generated edge routines, letting a local userCVE-2019-14566 · Intel SGX SDKHigh
• Intel SGX SDK (< 2.6.100.1): Improper initialisation in the SGX SDK gives an authenticated local user a privilegeCVE-2020-0561 · Intel SGX SDK (< 2.6.100.1)High
• AMD PSP trusted applications shipped in the AMD Graphics Driver: Trusted applications bundled with the AMD graphicsCVE-2020-12929 · AMD PSP trusted applications shipped in the AMD Graphics DriverHigh
• AMD Secure Processor (ASP) drivers: Improper parameter handling in the ASP driver layer lets an already-privilegedCVE-2020-12930 · AMD Secure Processor (ASP) driversHigh
• AMD Secure Processor (ASP) kernel: Improper parameter handling in the ASP's own kernel gives a privileged attackerCVE-2020-12931 · AMD Secure Processor (ASP) kernelHigh