drm/amdgpu/userq: fix access to stale wptr mapping
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 |
|
|
6.18.577.0.97.1In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/userq: fix access to stale wptr mapping
Use drm_exec to take both locks i.e vm root bo and wptr_obj bo to access the mapping data properly.
This fixes the security issue of unmap the wptr_obj while a queue creation is in progress and passing other bo at same address.
(cherry picked from commit 1fc6c8ab45dbee096469c08c13f6099d57a52d6c)
From the CVE record · Linux
The Linux kernel’s amdgpu user-queue code can access a stale write-pointer mapping during queue creation. This can occur if the write-pointer object is unmapped while the queue is being created and another buffer object is placed at the same address. The input does not specify authentication requirements or whether further user interaction is needed.
Operators running Linux kernels with the affected amdgpu user-queue code should check their kernel versions against the vendor advisory; affected versions were not provided.