KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d20c796ca3709801f8a7fa36e8770a3dd8ebd34e · < b53ab5167a81537777ac780bbd93d32613aa3bda| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12
svm_copy_lbrs() always marks VMCB_LBR dirty in the destination VMCB. However, nested_svm_vmexit() uses it to copy LBRs to vmcb12, and clearing clean bits in vmcb12 is not architecturally defined.
Move vmcb_mark_dirty() to callers and drop it for vmcb12.
This also facilitates incoming refactoring that does not pass the entire VMCB to svm_copy_lbrs().
From the CVE record · Linux
During a nested SVM VM exit, KVM can clear a VMCB_LBR clean bit in vmcb12, where clearing clean bits is not architecturally defined. The input does not specify an attacker action or whether network access, authentication, or user interaction is required.
Operators running the Linux kernel with KVM nSVM should check their kernel; affected versions are not specified.