Linux kernel amdgpu: recursive reservation lock in devcoredump can self-deadlock the coredump worker

UnscoredCVE-2026-80919NVIDIA / GPU stackcurated

Impact

When a job hangs, amdgpu_devcoredump_format() takes the VM root page directory's dma_resv via amdgpu_vm_lock_by_pasid() and then calls amdgpu_bo_reserve() on each IB buffer object, with no ww_acquire ticket shared between them. If an IB BO shares its dma_resv with the root PD - the always-valid case - the second acquire blocks on a lock the same worker already holds, wedging the events_unbound kernel worker that runs the deferred coredump. On a shared AMD GPU node this path is reached by any tenant whose job times out the engine, and a stuck kernel worker is not something an operator can clear without taking the node out of service. With amdgpu.gpu_recovery=0 the timeout handler refires roughly every two seconds and each pass emits a lockdep splat, drowning the kernel ring buffer and any logging that depends on it. In the trace quoted in the fix the two reservations are on different BOs, so what was observed there is the lockdep warning; the self-deadlock is the case the patch describes as real. The fix also removes a BO refcount leak on the amdgpu_bo_reserve() failure path.

Who can reach it

Local. Any tenant holding a GPU context on the node - an open amdgpu render node is enough, no elevated privilege - who can submit work that hangs the engine. No remote path.

What to do

Move to a stable kernel carrying one of the two linked commits. The amdgpu module cannot be unloaded while GPU workloads hold it, so in practice this means draining the node and rebooting into the patched kernel. The record names only the stable commits, not a fixed release number, so check your distro kernel's changelog rather than assuming a version.

References

https://nvd.nist.gov/vuln/detail/CVE-2026-80919 https://git.kernel.org/stable/c/4e9b4dee0777ec9c835a4746e2d30382dd9d1044 https://git.kernel.org/stable/c/7152b248dc3c8d5fa8629e99ed5655dd41b51562

Related entries

All NVIDIA / GPU stack entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.