VulnerabilityPublished 16 Sep 2026Updated 21 Oct 2026

CVE-2026-89813: Linux kernel · drm/amdgpu: force complete the KIQ ring fences on reset

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in fd65d1742992361fc2201ecb4e43411e6e417fcb : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in fd65d1742992361fc2201ecb4e43411e6e417fcb, c26cbd5c33cd72daa03079235de60688a3c97c52, bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 65781c78ad74e4260fbec92c0ecc05738044e177, < fd65d1742992361fc2201ecb4e43411e6e417fcb	Fixed in fd65d1742992361fc2201ecb4e43411e6e417fcb
LinuxLinux	Affected ≥ 65781c78ad74e4260fbec92c0ecc05738044e177, < c26cbd5c33cd72daa03079235de60688a3c97c52	Fixed in c26cbd5c33cd72daa03079235de60688a3c97c52
LinuxLinux	Affected ≥ 65781c78ad74e4260fbec92c0ecc05738044e177, < bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71	Fixed in bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71
LinuxLinux	Affected ≥ 65781c78ad74e4260fbec92c0ecc05738044e177, < 9944329e409b04d71fa22f39b38a4bd78b75bcd9	Fixed in 9944329e409b04d71fa22f39b38a4bd78b75bcd9
LinuxLinux	Affected ≥ 65781c78ad74e4260fbec92c0ecc05738044e177, < 11adb2bae30a3155395594e5c9bc0daf0c4ffa15	Fixed in 11adb2bae30a3155395594e5c9bc0daf0c4ffa15
LinuxLinux	Affected =4.13	Fixed in–

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.

References

Community reviews

Loading reviews…