diff options
author | Avi Kivity <avi@redhat.com> | 2009-03-23 16:13:44 -0400 |
---|---|---|
committer | Avi Kivity <avi@redhat.com> | 2009-03-24 05:03:15 -0400 |
commit | 16175a796d061833aacfbd9672235f2d2725df65 (patch) | |
tree | 69e1fb9865b3331f8a933fa9198b9245a914ea34 | |
parent | bc7a8660df62da3fb5cad025322eda75fbee8731 (diff) |
KVM: VMX: Don't allow uninhibited access to EFER on i386
vmx_set_msr() does not allow i386 guests to touch EFER, but they can still
do so through the default: label in the switch. If they set EFER_LME, they
can oops the host.
Fix by having EFER access through the normal channel (which will check for
EFER_LME) even on i386.
Reported-and-tested-by: Benjamin Gilbert <bgilbert@cs.cmu.edu>
Cc: stable@kernel.org
Signed-off-by: Avi Kivity <avi@redhat.com>
-rw-r--r-- | arch/x86/kvm/vmx.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c index 48063a0aa243..bb481330716f 100644 --- a/arch/x86/kvm/vmx.c +++ b/arch/x86/kvm/vmx.c | |||
@@ -936,11 +936,11 @@ static int vmx_set_msr(struct kvm_vcpu *vcpu, u32 msr_index, u64 data) | |||
936 | int ret = 0; | 936 | int ret = 0; |
937 | 937 | ||
938 | switch (msr_index) { | 938 | switch (msr_index) { |
939 | #ifdef CONFIG_X86_64 | ||
940 | case MSR_EFER: | 939 | case MSR_EFER: |
941 | vmx_load_host_state(vmx); | 940 | vmx_load_host_state(vmx); |
942 | ret = kvm_set_msr_common(vcpu, msr_index, data); | 941 | ret = kvm_set_msr_common(vcpu, msr_index, data); |
943 | break; | 942 | break; |
943 | #ifdef CONFIG_X86_64 | ||
944 | case MSR_FS_BASE: | 944 | case MSR_FS_BASE: |
945 | vmcs_writel(GUEST_FS_BASE, data); | 945 | vmcs_writel(GUEST_FS_BASE, data); |
946 | break; | 946 | break; |