diff options
| author | Sean Christopherson <[email protected]> | 2025-02-27 01:25:34 +0000 |
|---|---|---|
| committer | Sean Christopherson <[email protected]> | 2025-03-03 15:33:43 +0000 |
| commit | 72d12715edcd06cf1ef581c36633c44d43558f32 (patch) | |
| tree | 6528bc1da9e44b79dc40b36c5b9f35b2995c29f0 /tools/testing/selftests/net/lib/py/utils.py | |
| parent | KVM: SVM: Inject #GP if memory operand for INVPCID is non-canonical (diff) | |
| download | kernel-72d12715edcd06cf1ef581c36633c44d43558f32.tar.gz kernel-72d12715edcd06cf1ef581c36633c44d43558f32.zip | |
KVM: SVM: Refuse to attempt VRMUN if an SEV-ES+ guest has an invalid VMSA
Explicitly reject KVM_RUN with KVM_EXIT_FAIL_ENTRY if userspace "coerces"
KVM into running an SEV-ES+ guest with an invalid VMSA, e.g. by modifying
a vCPU's mp_state to be RUNNABLE after an SNP vCPU has undergone a Destroy
event. On Destroy or failed Create, KVM marks the vCPU HALTED so that
*KVM* doesn't run the vCPU, but nothing prevents a misbehaving VMM from
manually making the vCPU RUNNABLE via KVM_SET_MP_STATE.
Attempting VMRUN with an invalid VMSA should be harmless, but knowingly
executing VMRUN with bad control state is at best dodgy.
Fixes: e366f92ea99e ("KVM: SEV: Support SEV-SNP AP Creation NAE event")
Reviewed-by: Tom Lendacky <[email protected]>
Reviewed-by: Pankaj Gupta <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/utils.py')
0 files changed, 0 insertions, 0 deletions