In the Linux kernel, the following vulnerability has been resolved:<\/p>\n
KVM: nVMX: Always flush vpid02 on first use<\/p>\n
Make sure vpid02 is always flushed on first use by setting last_vpid=0
\nwhen allocating vpid02. nested_vmx_transition_tlb_flush() will always
\ndetect a VPID change on first VM-Enter after VMXON, because VPID=0 in
\nvmcs12 is not allowed if L1 enables VPID.<\/p>\n
This avoids using stale TLB entries from a previous lifetime of the
\nVPID, that might have been associated with a different vCPU (or a
\ncompletely different VM).<\/p>\n
Note that last_vpid is already being initialized as 0 when the vCPU is
\ncreated, but it is not reset when vpid02 is freed on VMXOFF. Hence, the
\nproblem can only occur if L1 does VMXOFF -> VMXON, runs an L2, and KVM
\nhappens to reuse a VPID that has TLB entries on the physical CPU.<\/p>\n","protected":false},"excerpt":{"rendered":"
In the Linux kernel, the following vulnerability has been resolved:<\/p>\n
KVM: nVMX: Always flush vpid02 on first use<\/p>\n
Make sure vpid02 is always flushed on first use by setting last_vpid=0
\nwhen allocating<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-24619","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/24619","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=24619"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=24619"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=24619"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}