CVE-2026-89813: drm/amdgpu: force complete the KIQ ring fences on reset
drm/amdgpu: force complete the KIQ ring fences on reset
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.114 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.57 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.6-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.12-1Fixed in 7.2.14-1 - Compensating control
On reset, force-complete the KIQ ring fences and realign their hardware fence value to fence_drv.sync_seq, so the first post-reset KIQ submission does not poll indefinitely.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using the Linux kernel AMDGPU driver are affected when the KIQ ring is used and the GPU undergoes a MODE1 reset. The failure can occur on the first KIQ submission after that reset.
What is the observable impact after a reset?
The first KIQ submission can poll indefinitely for a fence sequence value that is never written back. This can leave the KIQ operation stalled after the reset.
How can I determine whether this condition is present?
Investigate AMDGPU systems that experienced a MODE1 reset and subsequently show a KIQ submission polling indefinitely or failing to complete. The relevant condition is a mismatch between the KIQ hardware fence value retained in writeback memory and the advancing fence synchronization sequence.