UBUNTU-CVE-2026-89812: Medium severity ubuntu/linux-hwe-edge vulnerability
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: force complete the MES ring fences on reset The MES scheduler ring has no drm scheduler (noscheduler = true), so it is skipped by the force-completion loop in amdgpudevicepreasicreset(). It uses a polling fence whose hw value lives in wb (GTT) memory and survives a MODE1 reset, while fencedrv.syncseq keeps advancing for every packet. When the reset is triggered because MES itself stopped responding, the timed-out packets advance syncseq past the last hw fence value MES wrote. After resume the first MES submission polls forever on a seq that is never written back, failing the resume and wedging the box on a second reset: amdgpu: MES ring buffer is full. amdgpu: ERROR ring gfx0.0.0 test failed (-110) amdgpu: resume of IP block <gfxv110> failed -110 amdgpu: GPU reset end with ret = -110 Force complete the MES scheduler ring fences together with the scheduler rings so their hw fence is realigned to syncseq. v2: cover all XCCs (one scheduler ring each), not just mes.ring[0].
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
What access is required to exploit this issue?
The supplied severity vector indicates local access and low privileges are required, with no user interaction. It also indicates that the vulnerable component’s availability can be impacted, while confidentiality and integrity are not.
Which systems are most relevant for triage?
Prioritize systems using the AMDGPU driver’s MES scheduler ring on the listed Ubuntu kernel packages: linux-riscv, linux-realtime, linux-hwe-edge, linux-azure, linux-gcp, linux-azure-fde, linux-gke, and linux-aws-5.0. The failure path described occurs when MES stops responding and a GPU reset is performed.
How can I recognize the affected failure state?
After a GPU reset and resume, logs may show "MES ring buffer is full," a gfx ring test failure with "-110," and failure to resume the gfx_v11_0 IP block. A subsequent reset can wedge the system because the first MES submission polls for a fence sequence that is never written.