KVM: nSVM: always intercept VMLOAD/VMSAVE when nested (CVE-2021-3656)
authorMaxim Levitsky <mlevitsk@redhat.com>
Mon, 19 Jul 2021 13:05:00 +0000 (16:05 +0300)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 18 Aug 2021 06:59:18 +0000 (08:59 +0200)
commit3dc5666baf2a135f250e4101d41d5959ac2c2e1f
tree1eb0c78e4874e638a5aef674a7370da8acad2d68
parentc0883f693187c646c0972d73e525523f9486c2e3
KVM: nSVM: always intercept VMLOAD/VMSAVE when nested (CVE-2021-3656)

commit c7dfa4009965a9b2d7b329ee970eb8da0d32f0bc upstream.

If L1 disables VMLOAD/VMSAVE intercepts, and doesn't enable
Virtual VMLOAD/VMSAVE (currently not supported for the nested hypervisor),
then VMLOAD/VMSAVE must operate on the L1 physical memory, which is only
possible by making L0 intercept these instructions.

Failure to do so allowed the nested guest to run VMLOAD/VMSAVE unintercepted,
and thus read/write portions of the host physical memory.

Fixes: 89c8a4984fc9 ("KVM: SVM: Enable Virtual VMLOAD VMSAVE feature")

Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
arch/x86/kvm/svm/nested.c