Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
SUSE:SLE-12-SP3:GA
xen.4507
54467cfc-x86-hvm-further-restrict-x2apic-MSRs.p...
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File 54467cfc-x86-hvm-further-restrict-x2apic-MSRs.patch of Package xen.4507
# Commit 8d0a20587e4ebf3691ee88a55f91f398c4d2ee83 # Date 2014-10-21 17:34:20 +0200 # Author Andrew Cooper <andrew.cooper3@citrix.com> # Committer Jan Beulich <jbeulich@suse.com> x86/hvm: further restrict access to x2apic MSRs The x2apic specification reserves the entire MSR range 0x800-0xbff, while only the first 0x3f MSRs have defined purposes. All reserved MSRs in this region are architecturally required to raise #GP faults upon access. Xen used to pass this entire range to hvm_x2apic_msr_{read,write}(), but the range was restricted somewhat by XSA-108 (c/s 61fdda7ac) to prevent guests being able to read pages adjacent to the domheap page backing the vlapic->regs array. While removing the vulnerability, a side effect of XSA-108 was that the MSR range 0x900-0xbff fell through the switch statement and ends up reading the hosts x2apic range. This behaviour is a problem in general, but specifically it turns out that MSRs 0xa00-0xa02 are implemented (but undocumented) on certain SandyBridge and IvyBridge systems. Experimentally, no operating system in XenServer's test suite (including all versions of Windows currently supported by Microsoft) ever peek at these MSRs, even on hosts where some of them are implemented. This patch undoes the fix for XSA-108 (c/s 61fdda7ac), returning the primary bounds check to the entire specified range. hvm_x2apic_msr_write() was always safe, as it is whitelist based. hvm_x2apic_msr_read() changes to a whitelist approach, which avoids the vulnerability, and provides a more architecturally accurate emulation of the reserved MSRs (which would previously read as 0 rather than fault). Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> Reviewed-by: Jan Beulich <jbeulich@suse.com> Acked-by: Jun Nakajima <jun.nakajima@intel.com> Index: xen-4.4.4-testing/xen/arch/x86/hvm/hvm.c =================================================================== --- xen-4.4.4-testing.orig/xen/arch/x86/hvm/hvm.c +++ xen-4.4.4-testing/xen/arch/x86/hvm/hvm.c @@ -3111,7 +3111,7 @@ int hvm_msr_read_intercept(unsigned int *msr_content = vcpu_vlapic(v)->hw.apic_base_msr; break; - case MSR_IA32_APICBASE_MSR ... MSR_IA32_APICBASE_MSR + 0xff: + case MSR_IA32_APICBASE_MSR ... MSR_IA32_APICBASE_MSR + 0x3ff: if ( hvm_x2apic_msr_read(v, msr, msr_content) ) goto gp_fault; break; @@ -3238,7 +3238,7 @@ int hvm_msr_write_intercept(unsigned int vlapic_tdt_msr_set(vcpu_vlapic(v), msr_content); break; - case MSR_IA32_APICBASE_MSR ... MSR_IA32_APICBASE_MSR + 0xff: + case MSR_IA32_APICBASE_MSR ... MSR_IA32_APICBASE_MSR + 0x3ff: if ( hvm_x2apic_msr_write(v, msr, msr_content) ) goto gp_fault; break; Index: xen-4.4.4-testing/xen/arch/x86/hvm/vlapic.c =================================================================== --- xen-4.4.4-testing.orig/xen/arch/x86/hvm/vlapic.c +++ xen-4.4.4-testing/xen/arch/x86/hvm/vlapic.c @@ -648,16 +648,35 @@ int hvm_x2apic_msr_read(struct vcpu *v, if ( !vlapic_x2apic_mode(vlapic) ) return X86EMUL_UNHANDLEABLE; - vlapic_read_aligned(vlapic, offset, &low); switch ( offset ) { case APIC_ICR: vlapic_read_aligned(vlapic, APIC_ICR2, &high); + /* Fallthrough. */ + case APIC_ID: + case APIC_LVR: + case APIC_TASKPRI: + case APIC_PROCPRI: + case APIC_LDR: + case APIC_SPIV: + case APIC_ISR ... APIC_ISR + 0x70: + case APIC_TMR ... APIC_TMR + 0x70: + case APIC_IRR ... APIC_IRR + 0x70: + case APIC_ESR: + case APIC_CMCI: + case APIC_LVTT: + case APIC_LVTTHMR: + case APIC_LVTPC: + case APIC_LVT0: + case APIC_LVT1: + case APIC_LVTERR: + case APIC_TMICT: + case APIC_TMCCT: + case APIC_TDCR: + vlapic_read_aligned(vlapic, offset, &low); break; - case APIC_EOI: - case APIC_ICR2: - case APIC_SELF_IPI: + default: return X86EMUL_UNHANDLEABLE; }
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor