drm/amdgpu/userq: Fix fence reference leak on queue teardown v2
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: Fix fence reference leak on queue teardown v2
The user mode queue keeps a pointer to the most recent fence in userq->last_fence. This pointer holds an extra dma_fence reference.
When the queue is destroyed, we free the fence driver and its xarray, but we forgot to drop the last_fence reference.
Because of the missing dma_fence_put(), the last fence object can stay alive when the driver unloads. This leaves an allocated object in the amdgpu_userq_fence slab cache and triggers
This is visible during driver unload as:
BUG amdgpu_userq_fence: Objects remaining on __kmem_cache_shutdown() kmem_cache_destroy amdgpu_userq_fence: Slab cache still has objects Call Trace: kmem_cache_destroy amdgpu_userq_fence_slab_fini amdgpu_exit __do_sys_delete_module
Fix this by putting userq->last_fence and clearing the pointer during amdgpu_userq_fence_driver_free().
From the CVE record · Linux
The AMDGPU user-mode queue teardown fails to release a reference to its last fence. The fence object can remain allocated when the driver unloads, leaving objects in the slab cache; the input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running the Linux kernel with the AMDGPU driver should check their installations; affected versions are not specified.