{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-04-17T20:32:51.790","vulnerabilities":[{"cve":{"id":"CVE-2026-23034","sourceIdentifier":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","published":"2026-01-31T12:16:06.710","lastModified":"2026-04-15T00:35:42.020","vulnStatus":"Deferred","cveTags":[],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu/userq: Fix fence reference leak on queue teardown v2\n\nThe user mode queue keeps a pointer to the most recent fence in\nuserq->last_fence. This pointer holds an extra dma_fence reference.\n\nWhen the queue is destroyed, we free the fence driver and its xarray,\nbut we forgot to drop the last_fence reference.\n\nBecause of the missing dma_fence_put(), the last fence object can stay\nalive when the driver unloads. This leaves an allocated object in the\namdgpu_userq_fence slab cache and triggers\n\nThis is visible during driver unload as:\n\n  BUG amdgpu_userq_fence: Objects remaining on __kmem_cache_shutdown()\n  kmem_cache_destroy amdgpu_userq_fence: Slab cache still has objects\n  Call Trace:\n    kmem_cache_destroy\n    amdgpu_userq_fence_slab_fini\n    amdgpu_exit\n    __do_sys_delete_module\n\nFix this by putting userq->last_fence and clearing the pointer during\namdgpu_userq_fence_driver_free().\n\nThis makes sure the fence reference is released and the slab cache is\nempty when the module exits.\n\nv2: Update to only release userq->last_fence with dma_fence_put()\n    (Christian)\n\n(cherry picked from commit 8e051e38a8d45caf6a866d4ff842105b577953bb)"},{"lang":"es","value":"En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\ndrm/amdgpu/userq: Solución a la fuga de referencia de 'fence' durante el desmontaje de la cola v2\n\nLa cola en modo usuario mantiene un puntero al 'fence' más reciente en userq->last_fence. Este puntero mantiene una referencia extra de dma_fence.\n\nCuando la cola es destruida, liberamos el controlador de 'fence' y su xarray, pero olvidamos liberar la referencia de last_fence.\n\nDebido a la ausencia de dma_fence_put(), el último objeto 'fence' puede permanecer activo cuando el controlador se descarga. Esto deja un objeto asignado en la caché de 'slab' amdgpu_userq_fence y desencadena\n\nEsto es visible durante la descarga del controlador como:\n\n  BUG amdgpu_userq_fence: Objetos restantes en __kmem_cache_shutdown()\n  kmem_cache_destroy amdgpu_userq_fence: La caché de 'slab' todavía tiene objetos\n  Traza de Llamada:\n    kmem_cache_destroy\n    amdgpu_userq_fence_slab_fini\n    amdgpu_exit\n    __do_sys_delete_module\n\nSolucione esto liberando userq->last_fence y limpiando el puntero durante amdgpu_userq_fence_driver_free().\n\nEsto asegura que la referencia de 'fence' sea liberada y que la caché de 'slab' esté vacía cuando el módulo sale.\n\nv2: Actualización para liberar solo userq->last_fence con dma_fence_put() (Christian)\n\n(seleccionado del commit 8e051e38a8d45caf6a866d4ff842105b577953bb)"}],"metrics":{},"references":[{"url":"https://git.kernel.org/stable/c/b2426a211dba6432e32a2e70e9183c6e134475c6","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/e1a30e1ab33fc522785d04bbf7e1b13a5c5c9175","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}]}}]}