In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/userq: fix indefinite fence wait during GPU reset
prereset only force-completes fences of MAPPED queues. A queue in any other state (e.g. mid-eviction) keeps its lastfence pending; after a GPU reset that fence never signals, so the eviction/suspend worker and process teardown (amdgpuevfmgrflushsuspend) wait on it forever and wedge the machine:
INFO: task kworker/6:28 blocked for more than 120 seconds. Workqueue: events amdgpuevictionfencesuspendworker [amdgpu] Call Trace: dmafencewaittimeout+0x7e/0x130 amdgpuuserqevict+0x67/0x140 [amdgpu] amdgpuevictionfencesuspendworker+0xd8/0x160 [amdgpu] processscheduled_works+0xa6/0x420
Force-complete every queue's fence regardless of state. The unmap and mark-hung step stays gated on MAPPED, since unmapping a queue that is not mapped is invalid.
(cherry picked from commit 9102b39fa924dcc3dc75a3137bfa9633c40b88c0)
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68237.json",
"cna_assigner": "Linux"
}