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 90097 drivers hv vmbus skip vmbus module cleanup for
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
  • Affiliate program
  • 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-90097

Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partitionCVE-2026-90097

Answer in brief

CVE-2026-90097 records a Unknown severity vulnerability in Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition. 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 17, 2026Updated Oct 30, 2026Source checked Nov 1, 2026First seen by HOL Sep 17, 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
Nov 1, 2026
References
6 linked sources
Open source record

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
4 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). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=7e279d78664aa91107ebff4b03eca367967f5908 <aa17842bbccaeaba7d05c166019d1c96a41bca54 || >=7e279d78664aa91107ebff4b03eca367967f5908 <4c19c302cc577bd6b466f6d8e97971777392c2fa || >=7e279d78664aa91107ebff4b03eca367967f5908 <cee0d90bceae1dee3bcc70f8d6b2ceb5b87deb42aa17842bbccaeaba7d05c166019d1c96a41bca54, 4c19c302cc577bd6b466f6d8e97971777392c2fa, cee0d90bceae1dee3bcc70f8d6b2ceb5b87deb42
Linux/Linuxgeneric5.12Not reported
Linux/Linuxgeneric>=7e279d78664aa91107ebff4b03eca367967f5908 <4cc1ba2b31065a48fde14e9d53ad399a3ca32e35 || >=7e279d78664aa91107ebff4b03eca367967f5908 <ca1f4a926d08035c52c735a42200e4e5ea548f32 || >=7e279d78664aa91107ebff4b03eca367967f5908 <aa17842bbccaeaba7d05c166019d1c96a41bca54 || >=7e279d78664aa91107ebff4b03eca367967f5908 <4c19c302cc577bd6b466f6d8e97971777392c2fa || >=7e279d78664aa91107ebff4b03eca367967f5908 <cee0d90bceae1dee3bcc70f8d6b2ceb5b87deb424cc1ba2b31065a48fde14e9d53ad399a3ca32e35, ca1f4a926d08035c52c735a42200e4e5ea548f32, aa17842bbccaeaba7d05c166019d1c96a41bca54, 4c19c302cc577bd6b466f6d8e97971777392c2fa, cee0d90bceae1dee3bcc70f8d6b2ceb5b87deb42
Linux/Linuxgeneric>=7e279d78664aa91107ebff4b03eca367967f5908 <321f650493d6b8169dacd4d5d6f63550dce54d6c || >=7e279d78664aa91107ebff4b03eca367967f5908 <4cc1ba2b31065a48fde14e9d53ad399a3ca32e35 || >=7e279d78664aa91107ebff4b03eca367967f5908 <ca1f4a926d08035c52c735a42200e4e5ea548f32 || >=7e279d78664aa91107ebff4b03eca367967f5908 <aa17842bbccaeaba7d05c166019d1c96a41bca54 || >=7e279d78664aa91107ebff4b03eca367967f5908 <4c19c302cc577bd6b466f6d8e97971777392c2fa || >=7e279d78664aa91107ebff4b03eca367967f5908 <cee0d90bceae1dee3bcc70f8d6b2ceb5b87deb42321f650493d6b8169dacd4d5d6f63550dce54d6c, 4cc1ba2b31065a48fde14e9d53ad399a3ca32e35, ca1f4a926d08035c52c735a42200e4e5ea548f32, aa17842bbccaeaba7d05c166019d1c96a41bca54, 4c19c302cc577bd6b466f6d8e97971777392c2fa, cee0d90bceae1dee3bcc70f8d6b2ceb5b87deb42

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 aa17842bbccaeaba7d05c166019d1c96a41bca54; Linux/Linux to 4cc1ba2b31065a48fde14e9d53ad399a3ca32e35; Linux/Linux to 321f650493d6b8169dacd4d5d6f63550dce54d6c if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 17, 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 17, 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: Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition The VMBus module initialization function, hv_acpi_init(), currently does nothing when running in the root partition and root is not nested in another VM. But the initialization function reports success, so the VMBus module is indeed loaded. VMBus functionality is not actually needed, but the VMBus module must be loaded so that hv_vmbus_exists() can answer correctly. Furthermore, the mshv_root dependency on the VMBus module is needed as described in the commit message for 840b740a35bf ("mshv: Add conditional VMBus dependency"). Loading the VMBus module without actually initializing it causes failures if the module should later be unloaded. The module unload code tries to clean up things that were never initialized, resulting in memory faults and a panic. Fix this by having VMBus module exit function perform the same check for non-nested root partition, and do nothing in such a case, just like hv_acpi_init(). In the long run, the code that manages the Hyper-V provided SynIC should be refactored to better coordinate the requirements of root partition scenarios and normal VM scenarios, and to hopefully remove the hv_vmbus_exists() dependnecy between mshv_root and VMBus modules. Preventing the current unload failure scenario is an expediency until such a refactoring is done.

Quoted source text, attributed separately from HOL analysis.