---
id: "CVE-2026-98466"
kind: "vulnerability"
aliases: ["CVE-2026-98466"]
title: "Linux kernel KVM arm64: hypervisor stack pages left mapped to host"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["arm64", "infrastructure", "kvm", "linux-kernel", "self-hosted"]
not_affected_if: ["no-kvm", "x86-host"]
published_at: "2026-10-18T16:16:57+00:00"
first_seen_at: "2026-10-23T21:57:15+00:00"
updated_at: "2026-10-25T05:27:09+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98466", "first_seen_at": "2026-10-23T21:57:15+00:00"}]
---

# Linux kernel KVM arm64: hypervisor stack pages left mapped to host

In the Linux arm64 KVM hypervisor, the per-CPU hyp stack pages were not removed from the host stage-2 mapping during ownership transfer, because the fix walked only the linear-map alias and missed the private VA range. The sources do not state what an attacker gains from this beyond the mapping inconsistency.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- unknown

## Fix

- Update the Linux kernel to a release that includes the upstream commit titled 'KVM: arm64: Transfer the hyp stack pages out of the host stage-2' (version unknown from the sources)

## Timeline

- 2026-10-23T21:57:15+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98466

## From the sources

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: Transfer the hyp stack pages out of the host stage-2

fix_host_ownership() walks only the linear-map alias of each memblock
region, and the per-CPU hyp stack, mapped in the private VA range for
its guard page, has none.

Walk each stack's VA range with the same walker.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_