KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.17, 4.5, 6.6.160, 6.12.113, 6.18.56, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3.16.57 · fixed in 3.17; From 4.4.168 · fixed in 4.5
- Linux Linux
4.16
- KernelLinux
From 4.16.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10
References 8
git.kernel.org
- stable/c/001c78bc64389cabe4f9015ab3942ec9c3592caa
- stable/c/552a110c403f1a61eba0bf71519c6585d9d4242d
- stable/c/0e79ebf6f92a7d15187aede44204fa04b93e474c
- stable/c/84da7a0e92207444d9cbfe69965e17db29008f27
- stable/c/74836ae4785b9754bb36d0b18fcc1dec4e5e98d2
- stable/c/318ef696fa3c712e46bb62a1a828c3cd62f390c3
- stable/c/55865b3ae03705aa39198783b9cb1f8b96eb44e4
- stable/c/9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85