https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 21:27:47 +0000 https://vulnerability.circl.lu/vuln/cve-2026-23034 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdgpu/userq: Fix fence reference leak on queue teardown v2</p> <p>The user mode queue keeps a pointer to the most recent fence in userq-&gt;last_fence. This pointer holds an extra dma_fence reference.</p> <p>When the queue is destroyed, we free the fence driver and its xarray, but we forgot to drop the last_fence reference.</p> <p>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</p> <p>This is visible during driver unload as:</p> <p>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</p> <p>Fix this by putting userq-&gt;last_fence and clearing the pointer during amdgpu_userq_fence_driver_free().</p> <p>This makes sure the fence reference is released and the slab cache is empty when the module exits.</p> <p>v2: Update to only release userq-&gt;last_fence with dma_fence_put() (Christian)</p> <p>(cherry picked from commit 8e051e38a8d45caf6a866d4ff842105b577953bb)</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdgpu/userq: Fix fence reference leak on queue teardown v2</p> <p>The user mode queue keeps a pointer to the most recent fence in userq-&gt;last_fence. This pointer holds an extra dma_fence reference.</p> <p>When the queue is destroyed, we free the fence driver and its xarray, but we forgot to drop the last_fence reference.</p> <p>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</p> <p>This is visible during driver unload as:</p> <p>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</p> <p>Fix this by putting userq-&gt;last_fence and clearing the pointer during amdgpu_userq_fence_driver_free().</p> <p>This makes sure the fence reference is released and the slab cache is empty when the module exits.</p> <p>v2: Update to only release userq-&gt;last_fence with dma_fence_put() (Christian)</p> <p>(cherry picked from commit 8e051e38a8d45caf6a866d4ff842105b577953bb)</p> https://vulnerability.circl.lu/vuln/cve-2026-23034