In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: force complete the KIQ ring fences on reset Like the MES scheduler ring, the KIQ ring sets no_scheduler = true and uses a polling fence, so it is skipped by the force-completion loop in amdgpu_device_pre_asic_reset(). Its hw fence value lives in wb (GTT) memory and survives a MODE1 reset while fence_drv.sync_seq keeps advancing, so after a reset the first KIQ submission can poll forever on a seq that is never written back. Force complete the KIQ ring fences too so their hw fence is realigned to sync_seq.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 5
- StatusReceived → PublishedNVD modified 2026-10-21 12:48
- References+2 references (now 5)NVD modified 2026-10-21 13:20
- StatusPublished → ReceivedNVD modified 2026-10-21 13:20
- StatusReceived → PublishedNVD modified 2026-10-19 08:53
- First seenunscoredNVD modified 2026-10-15 11:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://git.kernel.org/stable/c/11adb2bae30a3155395594e5c9bc0daf0c4ffa15
- https://git.kernel.org/stable/c/9944329e409b04d71fa22f39b38a4bd78b75bcd9
- https://git.kernel.org/stable/c/bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71
- https://git.kernel.org/stable/c/c26cbd5c33cd72daa03079235de60688a3c97c52
- https://git.kernel.org/stable/c/fd65d1742992361fc2201ecb4e43411e6e417fcb