HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 89813 drmamdgpu force complete the kiq ring fences on
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright ยฉ 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Unknown severity ยท Source severity not reportedCVE-2026-89813

drm/amdgpu: force complete the KIQ ring fences on resetCVE-2026-89813

Answer in brief

CVE-2026-89813 records a Unknown severity vulnerability in drm/amdgpu: force complete the KIQ 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.

Published Sep 16, 2026Updated Oct 30, 2026Source checked Oct 31, 2026First seen by HOL Sep 16, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Oct 31, 2026
References
6 linked sources
Open source record

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
6 mapped packages or products
Fix availability
Available

Why this deserves its current priority

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.

Affected scope and exposure questions

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.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fd65d1742992361fc2201ecb4e43411e6e417fcb || >=0 <7.2.5bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71, fd65d1742992361fc2201ecb4e43411e6e417fcb, 7.2.5
Linux/Linuxgeneric>=65781c78ad74e4260fbec92c0ecc05738044e177 <bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71 || >=65781c78ad74e4260fbec92c0ecc05738044e177 <fd65d1742992361fc2201ecb4e43411e6e417fcbbdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71, fd65d1742992361fc2201ecb4e43411e6e417fcb
Linux/Linuxgeneric4.13Not reported
Linux/Linuxgeneric>=65781c78ad74e4260fbec92c0ecc05738044e177 <c26cbd5c33cd72daa03079235de60688a3c97c52 || >=65781c78ad74e4260fbec92c0ecc05738044e177 <bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71 || >=65781c78ad74e4260fbec92c0ecc05738044e177 <fd65d1742992361fc2201ecb4e43411e6e417fcbc26cbd5c33cd72daa03079235de60688a3c97c52, bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71, fd65d1742992361fc2201ecb4e43411e6e417fcb
Linux/Linuxgeneric>=65781c78ad74e4260fbec92c0ecc05738044e177 <11adb2bae30a3155395594e5c9bc0daf0c4ffa15 || >=65781c78ad74e4260fbec92c0ecc05738044e177 <9944329e409b04d71fa22f39b38a4bd78b75bcd9 || >=65781c78ad74e4260fbec92c0ecc05738044e177 <c26cbd5c33cd72daa03079235de60688a3c97c52 || >=65781c78ad74e4260fbec92c0ecc05738044e177 <bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71 || >=65781c78ad74e4260fbec92c0ecc05738044e177 <fd65d1742992361fc2201ecb4e43411e6e417fcb11adb2bae30a3155395594e5c9bc0daf0c4ffa15, 9944329e409b04d71fa22f39b38a4bd78b75bcd9, c26cbd5c33cd72daa03079235de60688a3c97c52, bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71, fd65d1742992361fc2201ecb4e43411e6e417fcb
Linux/Linuxgeneric>=65781c78ad74e4260fbec92c0ecc05738044e177 <83c54ed3be2f71a21e0f12ce5ca64435e33ba440 || >=65781c78ad74e4260fbec92c0ecc05738044e177 <11adb2bae30a3155395594e5c9bc0daf0c4ffa15 || >=65781c78ad74e4260fbec92c0ecc05738044e177 <9944329e409b04d71fa22f39b38a4bd78b75bcd9 || >=65781c78ad74e4260fbec92c0ecc05738044e177 <c26cbd5c33cd72daa03079235de60688a3c97c52 || >=65781c78ad74e4260fbec92c0ecc05738044e177 <bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71 || >=65781c78ad74e4260fbec92c0ecc05738044e177 <fd65d1742992361fc2201ecb4e43411e6e417fcb83c54ed3be2f71a21e0f12ce5ca64435e33ba440, 11adb2bae30a3155395594e5c9bc0daf0c4ffa15, 9944329e409b04d71fa22f39b38a4bd78b75bcd9, c26cbd5c33cd72daa03079235de60688a3c97c52, bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71, fd65d1742992361fc2201ecb4e43411e6e417fcb

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux, Linux/Linux.
  2. 2Review the reported fix. Update Linux/Linux to bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71; Linux/Linux to bdd6a58743e00ebc6d52b9cdf9aafb4e535e0b71; Linux/Linux to c26cbd5c33cd72daa03079235de60688a3c97c52; Linux/Linux to 11adb2bae30a3155395594e5c9bc0daf0c4ffa15; Linux/Linux to 83c54ed3be2f71a21e0f12ce5ca64435e33ba440 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 16, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Oct 30, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Sep 16, 2026

Sources and claim methodology

  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source 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.

Quoted source text, attributed separately from HOL analysis.