GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel KVM/arm64: guest-controlled TLBI Range can overflow the hypervisor's range computation

CVSS 7.9CVE-2026-89911Kernel, userspace & hypervisorcurated

Impact

TLB Invalidation by Range encodes very large ranges in few bits, based on a guest-chosen VA. KVM added that range to the base without capping it to the architectural limit dictated by the VA range bit, so a guest can overflow the computation. The consequence per the CVSS the kernel CNA assigned is mainly host availability with a scope change - a guest reaching outside its own boundary in what the hypervisor does on its behalf. On arm64 GPU hosts (Grace-Hopper and similar) running tenant VMs, that is a tenant able to disturb the host from inside a guest, on a node that cannot be drained cheaply. Exploitability beyond the availability impact is not established by the commit message.

Who can reach it

Local to the host, from inside a guest - any tenant holding a KVM guest on an arm64 host can issue the TLBI Range instructions that reach this path. No host credentials needed. x86 hosts are not affected.

What to do

Update to a stable kernel that caps the range to the architectural limit (IPA invalidation is further corrected downstream to ignore the upper range). This is a kernel-image fix, so arm64 virtualization hosts must be drained and rebooted; live-migrating guests off first avoids the tenant-visible outage. No mitigation short of not running untrusted guests on affected arm64 hosts.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.