CVE-2026-89813: drm/amdgpu: force complete the KIQ ring fences on reset
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 11adb2bae30a3155395594e5c9bc0daf0c4ffa15, 83c54ed3be2f71a21e0f12ce5ca64435e33ba440, 9944329e409b04d71fa22f39b38a4bd78b75bcd9; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 11adb2bae30a3155395594e5c9bc0daf0c4ffa15, 83c54ed3be2f71a21e0f12ce5ca64435e33ba440, 9944329e409b04d71fa22f39b38a4bd78b75bcd9; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 16, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.13affected
- 65781c78ad74e4260fbec92c0ecc05738044e177 and later · before 83c54ed3be2f71a21e0f12ce5ca64435e33ba440affected · git
- 65781c78ad74e4260fbec92c0ecc05738044e177 and later · before 11adb2bae30a3155395594e5c9bc0daf0c4ffa15affected · git
- 65781c78ad74e4260fbec92c0ecc05738044e177 and later · before 9944329e409b04d71fa22f39b38a4bd78b75bcd9affected · git
- 65781c78ad74e4260fbec92c0ecc05738044e177 and later · before c26cbd5c33cd72daa03079235de60688a3c97c52affected · git
- 65781c78ad74e4260fbec92c0ecc05738044e177 and later · before bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71affected · git
- 65781c78ad74e4260fbec92c0ecc05738044e177 and later · before fd65d1742992361fc2201ecb4e43411e6e417fcbaffected · git
- before 4.13not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89811Sep 16, 2026 · drm/amdkfd: Add TLB flush after MES queue eviction/suspension35Monitor
- ← EarlierCVE-2026-89812Sep 16, 2026 · drm/amdgpu: force complete the MES ring fences on reset0Monitor
- Later →CVE-2026-89814Sep 16, 2026 · drm/amdgpu: clamp the isolation index for rings outside a partition31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 11adb2bae30a3155395594e5c9bc0daf0c4ffa15 | Vendor (CNA) |
| Linux Linux | 83c54ed3be2f71a21e0f12ce5ca64435e33ba440 | Vendor (CNA) |
| Linux Linux | 9944329e409b04d71fa22f39b38a4bd78b75bcd9 | Vendor (CNA) |
| Linux Linux | bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71 | Vendor (CNA) |
| Linux Linux | c26cbd5c33cd72daa03079235de60688a3c97c52 | Vendor (CNA) |
| Linux Linux | fd65d1742992361fc2201ecb4e43411e6e417fcb | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/83c54ed3be2f71a21e0f12ce5ca64435e33ba440
- git.kernel.org/stable/c/9944329e409b04d71fa22f39b38a4bd78b75bcd9
- git.kernel.org/stable/c/bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71
- git.kernel.org/stable/c/c26cbd5c33cd72daa03079235de60688a3c97c52
- git.kernel.org/stable/c/fd65d1742992361fc2201ecb4e43411e6e417fcb
Vendor advisories and official records. Exploit/PoC links are deliberately left out.