drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9ae55f030dc523fc4dc6069557e4a887ea815453 · < 7150850146ebfa4ca998f653f264b8df6f7f85be| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib
amdgpu_amdkfd_submit_ib() submits a GPU job and gets a fence from amdgpu_ib_schedule(). This fence is used to wait for job completion.
Currently, the code drops the fence reference using dma_fence_put() before calling dma_fence_wait().
If dma_fence_put() releases the last reference, the fence may be freed before dma_fence_wait() is called. This can lead to a use-after-free.
Fix this by waiting on the fence first and releasing the reference only after dma_fence_wait() completes.
Fixes the below: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:697 amdgpu_amdkfd_submit_ib() warn: passing freed memory 'f' (line 696)
(cherry picked from commit 8b9e5259adc385b61a6590a13b82ae0ac2bd3482)
From the CVE record · Linux
The Linux kernel’s AMD GPU driver can release a job fence before waiting on it, causing a use-after-free if that was the last reference. The input does not specify how an attacker could trigger this or whether access or user interaction is required.
Engineers running Linux systems with the AMD GPU driver should check their kernel versions; affected versions are not specified.