Live › vulnerability › CVE-2026-98466
Go to dashboardIn 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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running Linux on arm64 hosts that use KVM to run virtual machines are the ones where this code path runs. Systems without KVM on arm64, and x86 hosts, are not affected by this code. The sources do not say which kernel versions are vulnerable.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98466")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.