CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's KVM (Kernel-based Virtual Machine) component, specifically concerning the management of Virtual Processor Identifiers (VPIDs) during nested virtualization. If a VPID is reused without proper flushing of stale Translation Lookaside Buffer (TLB) entries, it can lead to potential information leakage or incorrect execution contexts between virtual machines. Organizations utilizing Linux for virtualization, particularly those employing nested virtualization setups, should prioritize addressing this issue to ensure the integrity and isolation of their virtual environments.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Always flush vpid02 on first use Make sure vpid02 is always flushed on first use by setting last_vpid=0 when allocating vpid02. nested_vmx_transition_tlb_flush() will always detect a VPID change on first VM-Enter after VMXON, because VPID=0 in vmcs12 is not allowed if L1 enables VPID. This avoids using stale TLB entries from a previous lifetime of the VPID, that might have been associated with a different vCPU (or a completely different VM). Note that last_vpid is already being initialized as 0 when the vCPU is created, but it is not reset when vpid02 is freed on VMXOFF. Hence, the problem can only occur if L1 does VMXOFF -> VMXON, runs an L2, and KVM happens to reuse a VPID that has TLB entries on the physical CPU.