Linux kernel buffer validation bypass in AMDGPU user queues
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/userq: actually validate userq BOs
This was supposed to loop over the individual evicted list, as the kernel and always_valid evicted lists were already handled in amdgpu_vm_validate.
Without this, BOs that were created and evicted before a userq was made would never end up in an eviction fence rearm.
Also add the missing ref to the BO before drm_exec locks and refs it.
(cherry picked from commit 18decfc9e8cc0fa70b6de9944cc27a37729edfbd)
From the CVE record · Linux
The Linux kernel’s amdgpu user-queue code does not validate certain buffer objects created and evicted before a user queue is made, so they may miss eviction fence rearming. The input does not specify an attacker capability, security impact, authentication requirement, or whether access is local or network-based.
Teams running Linux kernels with amdgpu user queues should check their kernel; affected versions are not specified.