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 80726 kvm x86mmu warn and clear roleinvalid when
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
Critical ยท CVSS 9.3CVE-2026-80726

KVM: x86/mmu: WARN and clear role.invalid when creating a child shadow pageCVE-2026-80726

Answer in brief

CVE-2026-80726 records a Critical severity (CVSS 9.3) vulnerability in KVM: x86/mmu: WARN and clear role.invalid when creating a child shadow page. The current sources do not mark it as known exploited. The current feed maps 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 3, 2026Updated Oct 16, 2026Source checked Oct 18, 2026First seen by HOL Sep 3, 2026Material review Oct 16, 2026
Upstream Advisory

Key facts

Risk
Critical ยท CVSS 9.3
Exploitation
Not marked as known exploited
Affected software
3 mapped packages or products
Fix availability
Available

Why this deserves its current priority

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

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <ec4eb5c2ef964bf398f07889265121c316561911 || >=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <9b7984692c18b22d6d61af3f53887fca7fddb0f1 || >=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <f33ecb89d352348ed5e625f6747ac51ede254e1b || >=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <0af4711862c5b818204d40b21f0859ad51c230e9 || >=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <66bc868a33cf1de43f22a94acd8857e0fe33393f || >=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <9f7760a2e962cbda0d096a27d394d14ad4d22928 || >=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <5ec42d57655c690234c14aece6dd3f209778c1d8ec4eb5c2ef964bf398f07889265121c316561911, 9b7984692c18b22d6d61af3f53887fca7fddb0f1, f33ecb89d352348ed5e625f6747ac51ede254e1b, 0af4711862c5b818204d40b21f0859ad51c230e9, 66bc868a33cf1de43f22a94acd8857e0fe33393f, 9f7760a2e962cbda0d096a27d394d14ad4d22928, 5ec42d57655c690234c14aece6dd3f209778c1d8
Linux/Linuxgeneric>=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <9b7984692c18b22d6d61af3f53887fca7fddb0f1 || >=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <f33ecb89d352348ed5e625f6747ac51ede254e1b || >=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <0af4711862c5b818204d40b21f0859ad51c230e9 || >=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <66bc868a33cf1de43f22a94acd8857e0fe33393f || >=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <9f7760a2e962cbda0d096a27d394d14ad4d22928 || >=a770f6f28b1a9287189f3dc8333eb694d9a2f0ab <5ec42d57655c690234c14aece6dd3f209778c1d89b7984692c18b22d6d61af3f53887fca7fddb0f1, f33ecb89d352348ed5e625f6747ac51ede254e1b, 0af4711862c5b818204d40b21f0859ad51c230e9, 66bc868a33cf1de43f22a94acd8857e0fe33393f, 9f7760a2e962cbda0d096a27d394d14ad4d22928, 5ec42d57655c690234c14aece6dd3f209778c1d8
Linux/Linuxgeneric2.6.30Not reported

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 ec4eb5c2ef964bf398f07889265121c316561911; Linux/Linux to 9b7984692c18b22d6d61af3f53887fca7fddb0f1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 3, 2026

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

    Oct 16, 2026

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

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

In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: WARN and clear role.invalid when creating a child shadow page Explicitly clear role.invalid when deriving a child shadow page's role from its parent to harden against bugs elsewhere in KVM, as violating KVM's invariant that invalid pages are NOT on the list of active MMU pages leads to use-after-free due to __kvm_mmu_prepare_zap_page() using list_add() instead of list_move() when processing an invalid shadow page, i.e. makes a bad situation far worse. Yell loudly if the parent is invalid, as it means KVM has missed a validity check, i.e. KVM is attempting to map memory using an invalid/obsolete root, but continue on as the child is otherwise still a valid shadow page. ================================================================== BUG: KASAN: slab-use-after-free in __kvm_mmu_get_shadow_page+0x1817/0x1860 [kvm] Write of size 8 at addr ff11000153dd1368 by task repro/853 CPU: 1 UID: 1000 PID: 853 Comm: repro Not tainted 7.2.0-rc2-3aec122bdcaf-next-vm #5 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 Call Trace: <TASK> dump_stack_lvl+0x4b/0x70 print_report+0x153/0x49c kasan_report+0xbc/0xf0 __kvm_mmu_get_shadow_page+0x1817/0x1860 [kvm] mmu_alloc_root+0x141/0x320 [kvm] kvm_mmu_load+0x612/0x20f0 [kvm] kvm_arch_vcpu_ioctl_run+0x3dd5/0x6150 [kvm] kvm_vcpu_ioctl+0x5e4/0x10d0 [kvm] __x64_sys_ioctl+0x131/0x1b0 do_syscall_64+0x67/0x5f0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK> Allocated by task 853: kasan_save_stack+0x20/0x40 kasan_save_track+0x14/0x30 __kasan_slab_alloc+0x5f/0x70 kmem_cache_alloc_noprof+0xfe/0x2e0 __kvm_mmu_topup_memory_cache+0x135/0x530 [kvm] paging64_page_fault+0x318/0x1e30 [kvm] kvm_mmu_do_page_fault+0x21d/0x630 [kvm] kvm_mmu_page_fault+0x18c/0x17b0 [kvm] kvm_arch_vcpu_ioctl_run+0x1f35/0x6150 [kvm] kvm_vcpu_ioctl+0x5e4/0x10d0 [kvm] __x64_sys_ioctl+0x131/0x1b0 do_syscall_64+0x67/0x5f0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 Freed by task 853: kasan_save_stack+0x20/0x40 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x43/0x70 kmem_cache_free+0xe2/0x400 kvm_mmu_commit_zap_page.part.0+0x1e2/0x310 [kvm] kvm_mmu_free_roots+0x283/0x560 [kvm] kvm_arch_vcpu_ioctl_run+0x33c8/0x6150 [kvm] kvm_vcpu_ioctl+0x5e4/0x10d0 [kvm] __x64_sys_ioctl+0x131/0x1b0 do_syscall_64+0x67/0x5f0 entry_SYSCALL_64_after_hwframe+0x4b/0x53

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • WordPress Strong Testimonials plugin <= 3.3.12 - PHP Object Injection vulnerabilitySame generic ecosystem
  • WordPress Login with phone number plugin <= 1.8.77 - Privilege Escalation vulnerabilitySame generic ecosystem
  • WordPress Support Genix plugin <= 1.4.54 - SQL Injection vulnerabilitySame generic ecosystem
  • AUTOMATIC1111 stable-diffusion-webui Card Builder ui_extra_networks.py create_item_html cross site scriptingSame generic ecosystem
  • AUTOMATIC1111 stable-diffusion-webui Metadata Extraction sd_models.py read_metadata_from_safetensors allocation of resourcesSame generic ecosystem
  • AUTOMATIC1111 stable-diffusion-webui Model Instantiation sd_models.py get_obj_from_str code injectionSame generic ecosystem

Record context

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