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 89803 drmnouveau unsubscribe the channel kill event
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
High · CVSS 7.8CVE-2026-89803

drm/nouveau: unsubscribe the channel-kill event before the fence contextCVE-2026-89803

Answer in brief

CVE-2026-89803 records a High severity (CVSS 7.8) vulnerability in drm/nouveau: unsubscribe the channel-kill event before the fence context. 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). 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
High · CVSS 7.8
Exploitation
Not marked as known exploited
Affected software
4 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 7.8. 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). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e || >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <f3830fdd6930e233d727f29eee1617f7e6a0e9e5 || >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <1fef7553dc628295c1208a4f2ac2094c62886e5d || >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <511585987d27d8cb668acebd399fc4deda23404cf5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e, f3830fdd6930e233d727f29eee1617f7e6a0e9e5, 1fef7553dc628295c1208a4f2ac2094c62886e5d, 511585987d27d8cb668acebd399fc4deda23404c
Linux/Linuxgeneric5.6Not reported
Linux/Linuxgeneric>=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <5db663fbff7b88aeeeecaf5220e177e524165101 || >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e || >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <f3830fdd6930e233d727f29eee1617f7e6a0e9e5 || >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <1fef7553dc628295c1208a4f2ac2094c62886e5d || >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <511585987d27d8cb668acebd399fc4deda23404c5db663fbff7b88aeeeecaf5220e177e524165101, f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e, f3830fdd6930e233d727f29eee1617f7e6a0e9e5, 1fef7553dc628295c1208a4f2ac2094c62886e5d, 511585987d27d8cb668acebd399fc4deda23404c
Linux/Linuxgeneric>=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <ee1cfb1acdff3fe3b47de7c536e5c77443c8e74f || >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <5db663fbff7b88aeeeecaf5220e177e524165101 || >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e || >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <f3830fdd6930e233d727f29eee1617f7e6a0e9e5 || >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <1fef7553dc628295c1208a4f2ac2094c62886e5d || >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <511585987d27d8cb668acebd399fc4deda23404cee1cfb1acdff3fe3b47de7c536e5c77443c8e74f, 5db663fbff7b88aeeeecaf5220e177e524165101, f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e, f3830fdd6930e233d727f29eee1617f7e6a0e9e5, 1fef7553dc628295c1208a4f2ac2094c62886e5d, 511585987d27d8cb668acebd399fc4deda23404c

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 f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e; Linux/Linux to 5db663fbff7b88aeeeecaf5220e177e524165101; Linux/Linux to ee1cfb1acdff3fe3b47de7c536e5c77443c8e74f 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/nouveau: unsubscribe the channel-kill event before the fence context nouveau_channel_del() tears the fence context down first and only drops the channel-kill subscription later, in the middle of the nvif object teardown: if (chan->fence) nouveau_fence(chan->cli->drm)->context_del(chan); ... nvif_object_dtor(&chan->vram); nvif_event_dtor(&chan->kill); The subscribed handler is nouveau_channel_killed(), which calls nouveau_channel_kill() and from there nouveau_fence_context_kill() on chan->fence. A kill event delivered in that window takes fctx->lock and walks fctx->pending on a fence context that context_del() has already freed. Nothing reaches this below Fermi today, because the subscription is gated on FERMI_CHANNEL_GPFIFO and nothing kills a channel there. On Fermi and newer the window is real but narrow, since a kill has to land exactly while the channel is being destroyed. That is reason enough on its own, which is why this carries a Fixes: tag. The last patch in this series subscribes Tesla channels as well; nothing kills those today, so it does not widen the exposure now, but it is the groundwork for a recovery path that would, and the ordering is better fixed before that lands than alongside it. Drop the subscription before anything it depends on is torn down.

Quoted source text, attributed separately from HOL analysis.