CVE-2026-89813drm/amdgpu: force complete the KIQ ring fences on reset
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: force complete the KIQ ring fences on reset Like the MES scheduler ring, the KIQ ring sets no_scheduler = true and uses a polling fence, so it is skipped by the force-completion loop in amdgpu_device_pre_asic_reset(). Its hw fence value lives in wb (GTT) memory and survives a MODE1 reset while fence_drv.sync_seq keeps advancing, so after a reset the first KIQ submission can poll forever on a seq that is never written back. Force complete the KIQ ring fences too so their hw fence is realigned to sync_seq.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 44 days later
· 44 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 65781c78ad74e4260fbec92c0ecc05738044e177 – < 83c54ed3be2f71a21e0f12ce5ca64435e33ba440
- affected 65781c78ad74e4260fbec92c0ecc05738044e177 – < 11adb2bae30a3155395594e5c9bc0daf0c4ffa15
- affected 65781c78ad74e4260fbec92c0ecc05738044e177 – < 9944329e409b04d71fa22f39b38a4bd78b75bcd9
- affected 65781c78ad74e4260fbec92c0ecc05738044e177 – < c26cbd5c33cd72daa03079235de60688a3c97c52
- affected 65781c78ad74e4260fbec92c0ecc05738044e177 – < bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71
- affected 65781c78ad74e4260fbec92c0ecc05738044e177 – < fd65d1742992361fc2201ecb4e43411e6e417fcb
- affected 4.13
- unaffected < 4.13
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.5 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/83c54ed3be2f71a21e0f12ce5ca64435e33ba440 (opens in a new tab)
- https://git.kernel.org/stable/c/11adb2bae30a3155395594e5c9bc0daf0c4ffa15 (opens in a new tab)
- https://git.kernel.org/stable/c/9944329e409b04d71fa22f39b38a4bd78b75bcd9 (opens in a new tab)
- https://git.kernel.org/stable/c/c26cbd5c33cd72daa03079235de60688a3c97c52 (opens in a new tab)
- https://git.kernel.org/stable/c/bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71 (opens in a new tab)
- https://git.kernel.org/stable/c/fd65d1742992361fc2201ecb4e43411e6e417fcb (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-80413 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89813)Record last updated .