KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ cc3ed80ae69f454c3d904af9f65394a540099723 · < 0004ecb798b30e90d7ebfe74efae2d9423315a64| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation
Commit cc3ed80ae69f ("KVM: nSVM: always use vmcb01 to for vmsave/vmload of guest state") made KVM always use vmcb01 for the fields controlled by VMSAVE/VMLOAD, but it missed updating the VMLOAD/VMSAVE emulation code to always use vmcb01.
As a result, if VMSAVE/VMLOAD is executed by an L2 guest and is not intercepted by L1, KVM will mistakenly use vmcb02. Always use vmcb01 instead of the current VMCB.
From the CVE record · Linux
Linux KVM nSVM emulation can use vmcb02 instead of vmcb01 for VMLOAD/VMSAVE. An L2 guest can trigger this by executing VMLOAD or VMSAVE when the L1 guest does not intercept the instruction. The input does not specify an authentication requirement or user interaction.
Engineers running Linux kernels with KVM nSVM should check whether their kernel includes the fix; affected versions are not specified.