KVM: nVMX: Force MSR bitmap refresh if runtime eVMCS controls are modified
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
KVM nVMX can fail to refresh its MSR bitmap when runtime eVMCS controls change. If L1 does not intercept TPR writes and runs the same L2 first with TPR virtualization enabled and then disabled, L2—or L1 by proxy—can read and write L0’s TPR.
Engineers running the Linux kernel with KVM nVMX should check their systems; affected versions were not specified.