In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02's bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12. Don't bother tracking the virtual address of the bitmap that's being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.
https://git.kernel.org/stable/c/9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85
https://git.kernel.org/stable/c/84da7a0e92207444d9cbfe69965e17db29008f27
https://git.kernel.org/stable/c/74836ae4785b9754bb36d0b18fcc1dec4e5e98d2
https://git.kernel.org/stable/c/55865b3ae03705aa39198783b9cb1f8b96eb44e4
https://git.kernel.org/stable/c/552a110c403f1a61eba0bf71519c6585d9d4242d
https://git.kernel.org/stable/c/318ef696fa3c712e46bb62a1a828c3cd62f390c3
https://git.kernel.org/stable/c/0e79ebf6f92a7d15187aede44204fa04b93e474c
https://git.kernel.org/stable/c/001c78bc64389cabe4f9015ab3942ec9c3592caa