Answer in brief
CVE-2026-89812 records a Unknown severity vulnerability in drm/amdgpu: force complete the MES ring fences on reset. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ebe7542553d008e2285e0fbba0c63f0295a7e694 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <48dc279c3010ac8f91b1845b2abb3a1e9943a0f5 || >=0 <7.2.5 | ebe7542553d008e2285e0fbba0c63f0295a7e694, 48dc279c3010ac8f91b1845b2abb3a1e9943a0f5, 7.2.5 |
| Linux/Linuxgeneric | >=34e087e8920e635c62e2ed6a758b0cd27f836d13 <ebe7542553d008e2285e0fbba0c63f0295a7e694 || >=34e087e8920e635c62e2ed6a758b0cd27f836d13 <48dc279c3010ac8f91b1845b2abb3a1e9943a0f5 | ebe7542553d008e2285e0fbba0c63f0295a7e694, 48dc279c3010ac8f91b1845b2abb3a1e9943a0f5 |
| Linux/Linuxgeneric | 6.12 | Not reported |
| Linux/Linuxgeneric | >=34e087e8920e635c62e2ed6a758b0cd27f836d13 <7d722821e2f626c4e34c8510f0ce1d6f10c77a3b || >=34e087e8920e635c62e2ed6a758b0cd27f836d13 <ebe7542553d008e2285e0fbba0c63f0295a7e694 || >=34e087e8920e635c62e2ed6a758b0cd27f836d13 <48dc279c3010ac8f91b1845b2abb3a1e9943a0f5 | 7d722821e2f626c4e34c8510f0ce1d6f10c77a3b, ebe7542553d008e2285e0fbba0c63f0295a7e694, 48dc279c3010ac8f91b1845b2abb3a1e9943a0f5 |
| Linux/Linuxgeneric | >=34e087e8920e635c62e2ed6a758b0cd27f836d13 <c48d5a4d2863e56a6692ecb6cd6c32404f40cd0f || >=34e087e8920e635c62e2ed6a758b0cd27f836d13 <7d722821e2f626c4e34c8510f0ce1d6f10c77a3b || >=34e087e8920e635c62e2ed6a758b0cd27f836d13 <ebe7542553d008e2285e0fbba0c63f0295a7e694 || >=34e087e8920e635c62e2ed6a758b0cd27f836d13 <48dc279c3010ac8f91b1845b2abb3a1e9943a0f5 | c48d5a4d2863e56a6692ecb6cd6c32404f40cd0f, 7d722821e2f626c4e34c8510f0ce1d6f10c77a3b, ebe7542553d008e2285e0fbba0c63f0295a7e694, 48dc279c3010ac8f91b1845b2abb3a1e9943a0f5 |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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].
Quoted source text, attributed separately from HOL analysis.