Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
b2ac58f90540e39324e7a29a7ad471407ae0bf48 to < 84da7a0e92207444d9cbfe69965e17db29008f27affectedb2ac58f90540e39324e7a29a7ad471407ae0bf48 to < 74836ae4785b9754bb36d0b18fcc1dec4e5e98d2affectedb2ac58f90540e39324e7a29a7ad471407ae0bf48 to < 318ef696fa3c712e46bb62a1a828c3cd62f390c3affectedb2ac58f90540e39324e7a29a7ad471407ae0bf48 to < 55865b3ae03705aa39198783b9cb1f8b96eb44e4affectedb2ac58f90540e39324e7a29a7ad471407ae0bf48 to < 9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85affectedf54d0bb8487d2f016fbc4f0e38ef9098f8eb8bd4affected89be8950bab799ddb9cc3777345e3c21bcb32dbaaffected3.16.57 to < 3.17affected4.4.168 to < 4.5affected
Linux Linux
Default version status: affected
4.16affected0 to < 4.16unaffected6.6.160 to ≤ 6.6.*unaffected6.12.113 to ≤ 6.12.*unaffected6.18.56 to ≤ 6.18.*unaffected7.2.10 to ≤ 7.2.*unaffected7.3 to ≤ *unaffected
References
- https://git.kernel.org/stable/c/84da7a0e92207444d9cbfe69965e17db29008f27 ↗
- https://git.kernel.org/stable/c/74836ae4785b9754bb36d0b18fcc1dec4e5e98d2 ↗
- https://git.kernel.org/stable/c/318ef696fa3c712e46bb62a1a828c3cd62f390c3 ↗
- https://git.kernel.org/stable/c/55865b3ae03705aa39198783b9cb1f8b96eb44e4 ↗
- https://git.kernel.org/stable/c/9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85 ↗