KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded
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: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded
Leave control.erap_ctl and control.clean as-is in the VMCS if VMRUN fails, because as per AMD:
there's no explicit architectural guarantee about the behavior in the presence of VMRUN failures. So the best thing to do would be to assume that if VMRUN fails, the actions requested in the control fields may not have been performed.
From the CVE record · Linux
The Linux kernel’s KVM SVM code could update control fields after VMRUN fails, even though the requested actions may not have occurred. The input does not specify an attacker impact, access requirements, or whether user interaction is needed.
Engineers running Linux kernels with KVM SVM should check their versions; affected versions are not specified.