CVE-2026-23034 Details
Description
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(). This makes sure the fence reference is released and the slab cache is empty when the module exits. v2: Update to only release userq->last_fence with dma_fence_put() (Christian) (cherry picked from commit 8e051e38a8d45caf6a866d4ff842105b577953bb)
A vulnerability in the Linux kernel's AMDGPU driver has been addressed, concerning a fence reference leak during the teardown of user mode queues. The issue arises because the user queue maintains a pointer to the last fence, which holds an additional reference. When the queue is destroyed, the fence driver and its associated data structure are freed, but the reference to the last fence is not properly released. This oversight can cause the fence object to persist after the driver has been unloaded, leaving a memory allocation in the AMDGPU user queue fence slab cache. The problem becomes apparent during the driver unload process, which reveals remaining objects in the slab cache, indicating a failure to properly clean up. The vulnerability has been fixed by ensuring that the last fence reference is released and the pointer cleared before the user queue is fully destroyed, allowing the slab cache to be emptied before the module exits.
Users can apply the latest patches from the Linux kernel stable tree to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Jan 31, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/b2426a211dba6432e32a2e70e9183c6e134475c6 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/e1a30e1ab33fc522785d04bbf7e1b13a5c5c9175 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jan 31, 2026 | New CVE Received | kernel.org |
Volerion