KVM: nVMX: Force MSR bitmap refresh if runtime eVMCS controls are modified
- 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 6.12.113, 6.18.56, 7.2.10
- 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: nVMX: Force MSR bitmap refresh if runtime eVMCS controls are modified Force a refresh of the vmcs02 MSR bitmap during nested VM-Enter if the runtime eVMCS controls (pin, primary, secondary, etc.) are being updated. If L1 isn't intercepting TPR writes, runs L2 with TPR virtualization, and then runs the same L2 with TPR virtualization disabled, KVM will fail to refresh msr_bitmap02 and leave TPR in passthrough mode even though TPR virtualization is disabled. I.e. failure to refresh the bitmap lets L2 (or L1 by proxy) read and write L0's TPR.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 502d2bf5f2fd7c05adc2d4f057910bd5d4c4c63e · fixed in 2db11598b59f16ddb6420693f9a4ac4efc3d4789; From 502d2bf5f2fd7c05adc2d4f057910bd5d4c4c63e · fixed in f6189e26d0237e47e2f04f9cb1e43fd19a9b2f3a; From 502d2bf5f2fd7c05adc2d4f057910bd5d4c4c63e · fixed in 1e497e3bdab6983deb68a1d26b488027deb4527f; From 502d2bf5f2fd7c05adc2d4f057910bd5d4c4c63e · fixed in 2abb25273c82061dd4670690c81c319c03740bf6
- Linux Linux
5.17
- KernelLinux
From 5.17.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10