CVE-2026-99624: drm/amdgpu: Report MES ring wait timeouts.
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: Report MES ring wait timeouts.
Return -ETIMEDOUT when the fence wait before submission expires instead of reporting success without submitting the packet.
(cherry picked from commit 34341594a87b4a3f28be41e3e70a4787f02b3d9e)
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.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 7.3.5-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch 34341594a87b4a3f28be41e3e70a4787f02b3d9e
Event History
Frequently Asked Questions
What is the observable impact when this condition occurs?
If the fence wait before packet submission expires, affected code can report success even though the packet was not submitted. The resolved behavior returns -ETIMEDOUT instead.
How can I identify the condition in an updated kernel?
An updated kernel reports the failure as -ETIMEDOUT when the MES ring fence wait expires before submission. This distinguishes the timeout from a successful submission.