CVE-2026-89813

drm/amdgpu: force complete the KIQ ring fences on reset

Published Sep 16, 2026 CVSS n/a EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The amdgpu driver does not complete KIQ ring fences when a graphics reset occurs, causing the first submission after a reset to poll indefinitely on a sequence number that is never updated. This leads to an infinite wait that can exhaust system resources and degrade or halt GPU responsiveness, effectively denying access to graphic services. The weakness arises from improper synchronization handling, making the GPU ring state stale across a reset.

Affected Systems

Linux kernel implementations that include the amdgpu DRM driver are affected. No specific kernel versions are listed; any distribution that ships the unpatched kernel includes the flaw.

Risk and Exploitability

The flaw is local to systems running the affected kernel, as execution of GPU commands is required to trigger the conditions. The EPSS score of less than 1% suggests a low probability of active exploitation, and the vulnerability is not in the CISA KEV catalog. However, once triggered, the impact is a denial of service that can bring the entire GPU subsystem to a halt. Attackers would need the ability to submit graphics work or otherwise induce a reset, which typically requires local user privileges or compromised software.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the amdgpu KIQ ring fence completion fix (e.g., a kernel where commits bdd6a587… and fd65d174… have been merged).
  • If a kernel upgrade is not immediately possible, limit GPU participation to privileged users or disable the ability for user processes to trigger graphics resets, effectively preventing the conditions that cause the hang.
  • Continuously monitor GPU logs and resource usage to detect prolonged polling or latency spikes that may indicate a stuck command sequence.

Generated by OpenCVE AI on September 18, 2026 at 09:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
Debian DLA Debian DLA DLA-4906-1 linux security update
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-400
Type Values Removed Values Added
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.
Title drm/amdgpu: force complete the KIQ ring fences on reset
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:33 PM
Reserved
Sep 11, 2026, 7:38 PM
Status
Received
Published
Sep 16, 2026, 11:16 AM
Modified
Oct 30, 2026, 1:20 PM