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 64561 kvm x86 check for invalidobsolete root after
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
  • Contribute to HOL
  • 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
High · CVSS 8.8CVE-2026-64561

KVM: x86: Check for invalid/obsolete root *after* making MMU pages availableCVE-2026-64561

Answer in brief

CVE-2026-64561 records a High severity (CVSS 8.8) vulnerability in KVM: x86: Check for invalid/obsolete root *after* making MMU pages available. 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 Aug 4, 2026Updated Nov 3, 2026Source checked Nov 6, 2026First seen by HOL Aug 4, 2026Material review Nov 3, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 8.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 8.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>=f95eec9bed76d42194c23153cb1cc8f186bf91cb <35e77467610c4a37cb0ff54ee56b85f73b1f5700 || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <0026dbb7de8ea76e97d6edf42fc3cc084564e2bf || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <f3477a6a4164f15287444eda685b5f6405dbd1e5 || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <bce0d3c26e2c761a4bf43c8949f333fc7374eb2d || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <2abd5287f08319fa35764566b15c6e22cb1068db35e77467610c4a37cb0ff54ee56b85f73b1f5700, 0026dbb7de8ea76e97d6edf42fc3cc084564e2bf, f3477a6a4164f15287444eda685b5f6405dbd1e5, bce0d3c26e2c761a4bf43c8949f333fc7374eb2d, 2abd5287f08319fa35764566b15c6e22cb1068db
Linux/Linuxgeneric>=f95eec9bed76d42194c23153cb1cc8f186bf91cb <65c4f7a1028cf01a93a2762d679c289810ede990 || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <35e77467610c4a37cb0ff54ee56b85f73b1f5700 || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <0026dbb7de8ea76e97d6edf42fc3cc084564e2bf || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <f3477a6a4164f15287444eda685b5f6405dbd1e5 || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <bce0d3c26e2c761a4bf43c8949f333fc7374eb2d || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <2abd5287f08319fa35764566b15c6e22cb1068db65c4f7a1028cf01a93a2762d679c289810ede990, 35e77467610c4a37cb0ff54ee56b85f73b1f5700, 0026dbb7de8ea76e97d6edf42fc3cc084564e2bf, f3477a6a4164f15287444eda685b5f6405dbd1e5, bce0d3c26e2c761a4bf43c8949f333fc7374eb2d, 2abd5287f08319fa35764566b15c6e22cb1068db
Linux/Linuxgeneric5.9Not reported
Linux/Linuxgeneric>=f95eec9bed76d42194c23153cb1cc8f186bf91cb <62ef67af1878fa2cd066642f2f59e33ade95f637 || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <65c4f7a1028cf01a93a2762d679c289810ede990 || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <35e77467610c4a37cb0ff54ee56b85f73b1f5700 || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <0026dbb7de8ea76e97d6edf42fc3cc084564e2bf || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <f3477a6a4164f15287444eda685b5f6405dbd1e5 || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <bce0d3c26e2c761a4bf43c8949f333fc7374eb2d || >=f95eec9bed76d42194c23153cb1cc8f186bf91cb <2abd5287f08319fa35764566b15c6e22cb1068db62ef67af1878fa2cd066642f2f59e33ade95f637, 65c4f7a1028cf01a93a2762d679c289810ede990, 35e77467610c4a37cb0ff54ee56b85f73b1f5700, 0026dbb7de8ea76e97d6edf42fc3cc084564e2bf, f3477a6a4164f15287444eda685b5f6405dbd1e5, bce0d3c26e2c761a4bf43c8949f333fc7374eb2d, 2abd5287f08319fa35764566b15c6e22cb1068db

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 35e77467610c4a37cb0ff54ee56b85f73b1f5700; Linux/Linux to 65c4f7a1028cf01a93a2762d679c289810ede990; Linux/Linux to 62ef67af1878fa2cd066642f2f59e33ade95f637 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 4, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Nov 3, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Aug 4, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • Source referencegit.kernel.org
  • 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: KVM: x86: Check for invalid/obsolete root *after* making MMU pages available Check for a "stale" page fault, i.e. for an invalid and/or obsolete root, after making MMU pages available for the shadow MMU. If reclaiming shadow pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to map memory into an invalid root. On its own, populating an invalid root is "fine", but because child shadow pages inherit their parent's role, any children created during the map/fetch will be created as invalid pages, thus violating KVM's invariant that invalid pages are never on the list of active MMU pages. Note, the underlying flaw has existed since KVM first started tracking invalid roots in 2008 (commit 2e53d63acba7, "KVM: MMU: ignore zapped root pagetables"), but the true badness only came along in 2020 (Linux 5.9) with the invariant that invalid shadow pages can't be on the list of active pages. Note #2, inheriting role.invalid when creating child shadow pages is also far from ideal; that flaw will be addressed separately.

Quoted source text, attributed separately from HOL analysis.

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
CWE-362
Source
CVE List V5
Source checked
Nov 6, 2026
References
8 linked sources
Open source record