KVM: SVM: SEV{-ES} bug fixes
Status from this message: Queued, thanks.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | KVM: SVM: Use online_vcpus, not created_vcpus, to iterate over vCPUsarch/ | +3 | 0 replies | |
| 2/3 | KVM: SVM: Do not set sev->es_active until KVM_SEV_ES_INIT completesarch/ | +12 | 0 replies | |
| 3/3 | KVM: SVM: Do not allow SEV/SEV-ES initialization after vCPUs are createdarch/ | +3 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] KVM: SVM: SEV{-ES} bug fixes
Misc bug fixes in SEV/SEV-ES to protect against a malicious userspace. All found by inspection, I didn't actually crash the host to to prove that userspace could hose the kernel in any of these cases. Boot tested an SEV guest, though the SEV-ES side of patch 2 is essentially untested as I don't have an SEV-ES setup at this time.
Sean Christopherson (3):
KVM: SVM: Use online_vcpus, not created_vcpus, to iterate over vCPUs
KVM: SVM: Do not set sev->es_active until KVM_SEV_ES_INIT completes
KVM: SVM: Do not allow SEV/SEV-ES initialization after vCPUs are
created
arch/x86/kvm/svm/sev.c | 37 ++++++++++++++++++------------------- 1 file changed, 18 insertions(+), 19 deletions(-)
Signature · 1 line
2.31.0.291.g576ba9dcdaf-goog