GPU VulnDB

Database/Kernel, userspace & hypervisor

KVM arm64: missing VA sign extension in range-based TLB invalidation decoding

CVSS 9.3CVE-2026-89914Kernel, userspace & hypervisorcurated

Impact

When decode_range_tlbi() was reused for stage-1 TLB invalidations, the required sign extension of the virtual address was left out, so the address range KVM computes for a range-based TLBI does not match what the guest asked to invalidate. Entries that should be flushed can be left in place, letting a nested guest continue to use translations it believes are gone - and the fix note warns that the same helper must avoid overflowing PA bits when used for stage-2. This is a separate defect from the VNCR level-sizing bug (CVE-2026-89775) in the same release, with its own commits, though both are in arm64 nested-virt TLBI handling and both are fixed by the same kernel update. Exposure is limited to arm64 KVM hosts running nested virtualization.

Who can reach it

A guest on an arm64 KVM host with nested virtualization enabled, issuing range-based TLB invalidations. No host credentials required.

What to do

Install the patched kernel containing the three listed commits and reboot affected arm64 KVM hosts with guests drained or migrated. Leaving nested virtualization disabled on arm64 avoids the affected path. No fixed distribution version is given in the record.

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.