GPU VulnDB

Database/Control plane, storage & DevOps

AMD Graphics Driver - crafted pointer leading to arbitrary code execution: MULTI-TENANT ISOLATION: Improper input

CVE-2024-36324Control plane, storage & DevOpscurated

Impact

MULTI-TENANT ISOLATION: Improper input validation in the AMD graphics driver lets an attacker supply a crafted pointer and reach arbitrary code execution. At 8.8 this is the most severe of AMD's own graphics-driver advisories in the window: a pointer that crosses the driver boundary unvalidated means kernel-level execution from whatever context can issue the call.

Who can reach it

Local, via the graphics driver interface - reachable by a process holding the GPU device.

What to do

Update the AMD graphics driver package, then reload the driver or reboot. Confirm the fixed version is present in the ROCm/amdgpu build you actually deploy, since the packaged AMD driver and the mainline kernel driver move on different schedules.

References

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.