Description
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 (no_scheduler = true), so it is skipped by the force-completion loop in amdgpu_device_pre_asic_reset(). It uses a polling fence whose hw value lives in wb (GTT) memory and survives a MODE1 reset, while fence_drv.sync_seq keeps advancing for every packet.
When the reset is triggered because MES itself stopped responding, the timed-out packets advance sync_seq 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 gfx_0.0.0 test failed (-110) amdgpu: resume of IP block <gfx_v11_0> 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 sync_seq.
v2: cover all XCCs (one scheduler ring each), not just mes.ring[0].
Metrics
No CVSS score has been published yet.
Affected software
Source: the vendor's advisory (CNA). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 34e087e8920e635c62e2ed6a758b0cd27f836d13, < c48d5a4d2863e56a6692ecb6cd6c32404f40cd0f; >= 34e087e8920e635c62e2ed6a758b0cd27f836d13, < 7d722821e2f626c4e34c8510f0ce1d6f10c77a3b; >= 34e087e8920e635c62e2ed6a758b0cd27f836d13, < ebe7542553d008e2285e0fbba0c63f0295a7e694; >= 34e087e8920e635c62e2ed6a758b0cd27f836d13, < 48dc279c3010ac8f91b1845b2abb3a1e9943a0f5 |
| Linux | Linux | 6.12 |
References
Timeline
- Published
- Sep 16, 2026
- Last modified
- Oct 21, 2026
- NVD status
- Received