Skip to main content
Vulnerability Database/CVE-2026-98466

CVE-2026-98466: Linux Kernel KVM Privilege Escalation Flaw

CVE-2026-98466 is a privilege escalation vulnerability in the Linux kernel KVM affecting ARM64 architecture. The flaw involves improper handling of hyp stack pages in host stage-2. This article covers technical details, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-98466 Overview

CVE-2026-98466 is a Linux kernel vulnerability in the KVM arm64 subsystem. The flaw resides in how fix_host_ownership() handles per-CPU hypervisor stack pages during stage-2 memory configuration. The function walks only the linear-map alias of each memblock region. However, per-CPU hyp stacks are mapped in the private virtual address (VA) range to accommodate a guard page, so they lack a linear-map alias. As a result, these stack pages are not properly transferred out of the host stage-2 translation, leaving them accessible to the host when they should belong exclusively to the hypervisor.

Critical Impact

Host-accessible hypervisor stack pages weaken the stage-2 isolation boundary that protects pKVM hypervisor memory from the host kernel on arm64 systems.

Affected Products

  • Linux kernel KVM arm64 subsystem (pKVM / protected KVM)
  • Upstream Linux kernel versions prior to the referenced stable commits
  • Linux distributions shipping affected kernel branches for arm64

Discovery Timeline

  • 2026-10-18 - CVE-2026-98466 published to NVD
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-98466

Vulnerability Analysis

The vulnerability affects the protected KVM (pKVM) initialization path on arm64. During boot, the hypervisor must take exclusive ownership of memory regions that back its own data structures. fix_host_ownership() performs this transfer by walking memblock regions through their linear-map aliases and updating stage-2 page tables so the host no longer has access.

Per-CPU hypervisor stacks are allocated with a trailing guard page and are mapped into the private hypervisor VA range. Because they are not reachable through the linear map, the existing walker skips them entirely. The host stage-2 therefore retains mappings to pages the hypervisor is actively using as its own stack.

This breaks the isolation guarantee that pKVM relies on. The host kernel, which pKVM treats as untrusted, retains access to memory that holds hypervisor execution state. The fix walks each stack's VA range with the same ownership-transfer walker so these pages are properly removed from the host stage-2.

Root Cause

The root cause is incomplete coverage in the stage-2 ownership transfer logic. The walker iterates linear-map aliases of memblock regions and assumes every page belonging to the hypervisor is reachable that way. Per-CPU hyp stacks violate that assumption because they are mapped only in the private VA range to allow a guard page. The omission is a design-level oversight in how hypervisor-owned memory is enumerated rather than a memory-safety bug in the traditional sense.

Attack Vector

Exploitation requires local privileges on the host kernel of an arm64 system running pKVM. A privileged host component with access to the stage-2 mappings of hypervisor stack pages could read or modify data that should be isolated to the hypervisor. The flaw is relevant to confidential-computing deployments that rely on pKVM to protect guest memory from a compromised host. The NVD entry does not provide a CVSS score, and no public proof-of-concept exploit is referenced.

No verified code example is available. The upstream fix is distributed across kernel commits 22df195, 3a8c562, and e5dd2a9. See the Kernel Git Commit 22df195 for implementation details.

Detection Methods for CVE-2026-98466

Indicators of Compromise

  • No specific indicators of compromise have been published for this vulnerability.
  • Exploitation would occur in-kernel on arm64 pKVM hosts and would not produce standard log artifacts.

Detection Strategies

  • Inventory arm64 systems running KVM and determine which boot with the pKVM protected mode enabled.
  • Compare running kernel versions and build identifiers against the fixed stable commits 22df195, 3a8c562, and e5dd2a9.
  • Use configuration management tooling to flag hosts that have not received distribution kernel updates addressing the fix.

Monitoring Recommendations

  • Monitor kernel package versions on arm64 virtualization hosts and alert on drift from patched baselines.
  • Track vendor security advisories for downstream kernels that backport the pKVM stage-2 ownership fix.
  • Audit workloads that depend on pKVM confidentiality guarantees and verify they run only on patched kernels.

How to Mitigate CVE-2026-98466

Immediate Actions Required

  • Update the Linux kernel on arm64 hosts to a version that includes the upstream fix referenced by the kernel.org stable commits.
  • Prioritize patching on systems that use pKVM to isolate confidential or multi-tenant guest workloads.
  • Reboot affected hosts after kernel updates to activate the corrected stage-2 ownership transfer logic.

Patch Information

The upstream fix walks each hypervisor stack's VA range with the same walker used for memblock regions, ensuring stack pages are transferred out of the host stage-2. Reference commits: 22df195, 3a8c562, and e5dd2a9. Distribution-specific kernel updates should be applied through standard package management channels.

Workarounds

  • Disable pKVM protected mode on arm64 hosts where the confidentiality guarantee is not required, until patched kernels are deployed.
  • Restrict local privileged access on affected hosts to reduce the population of actors who could abuse the stage-2 exposure.
  • Where feasible, migrate sensitive guest workloads to hosts already running patched kernels.
bash
# Verify running kernel version on an arm64 host
uname -r

# Example: apply vendor kernel updates (Debian/Ubuntu)
sudo apt update && sudo apt install --only-upgrade linux-image-$(uname -r | sed 's/-generic//')-generic
sudo reboot

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.