CVE-2015-2045

This xen update is based on upstream 4.5.2 maintenance release, and fixes the following security issues:

The vgic_v2_to_sgi function in arch/arm/vgic-v2.c in Xen 4.5.x, when running on ARM hardware with general interrupt controller (GIC) version 2, allows local guest users to cause a denial of service (host crash) by writing an invalid value to the GICD.SGIR register (CVE-2015-0268).

The ARM GIC distributor virtualization in Xen 4.4.x and 4.5.x allows local guests to cause a denial of service by causing a large number messages to be logged (CVE-2015-1563).

The emulation routines for unspecified X86 devices in Xen 3.2.x through 4.5.x does not properly initialize data, which allow local HVM guest users to obtain sensitive information via vectors involving an unsupported access size (CVE-2015-2044).

The HYPERVISOR_xen_version hypercall in Xen 3.2.x through 4.5.x does not properly initialize data structures, which allows local guest users to obtain sensitive information via unspecified vectors (CVE-2015-2045).

Xen 3.3.x through 4.5.x and the Linux kernel through 3.19.1 do not properly restrict access to PCI command registers, which might allow local guest users to cause a denial of service (non-maskable interrupt and host crash) by disabling the (1) memory or (2) I/O decoding for a PCI Express device and then accessing the device, which triggers an Unsupported Request (UR) response (CVE-2015-2150).

The x86 emulator in Xen 3.2.x through 4.5.x does not properly ignore segment overrides for instructions with register operands, which allows local guest users to obtain sensitive information, cause a denial of service (memory corruption), or possibly execute arbitrary code via unspecified vectors (CVE-2015-2151).

Xen 4.5.x and earlier enables certain default backends when emulating a VGA device for an x86 HVM guest qemu even when the configuration disables them, which allows local guest users to obtain access to the VGA console by (1) setting the DISPLAY environment variable, when compiled with SDL support, or connecting to the VNC server on (2) ::1 or (3) 127.0.0.1, when not compiled with SDL support (CVE-2015-2152).

Xen 4.3.x, 4.4.x, and 4.5.x, when using toolstack disaggregation, allows remote domains with partial management control to cause a denial of service (host lock) via unspecified domctl operations (CVE-2015-2751).

The XEN_DOMCTL_memory_mapping hypercall in Xen 3.2.x through 4.5.x, when using a PCI passthrough device, is not preemptable, which allows local x86 HVM domain users to cause a denial of service (host CPU consumption) via a crafted request to the device model (qemu-dm) (CVE-2015-2752).

QEMU, as used in Xen 3.3.x through 4.5.x, does not properly restrict access to PCI command registers, which might allow local HVM guest users to cause a denial of service (non-maskable interrupt and host crash) by disabling the (1) memory or (2) I/O decoding for a PCI Express device and then accessing the device, which triggers an Unsupported Request (UR) response (CVE-2015-2756).

Heap-based buffer overflow in the PCNET controller in QEMU allows remote attackers to execute arbitrary code by sending a packet with TXSTATUS_STARTPACKET set and then a crafted packet with TXSTATUS_DEVICEOWNS set (CVE-2015-3209).

Stack-based buffer overflow in the xl command line utility in Xen 4.1.x through 4.5.x allows local guest administrators to gain privileges via a long configuration argument (CVE-2015-3259).

Xen 4.2.x through 4.5.x does not initialize certain fields, which allows certain remote service domains to obtain sensitive information from memory via a (1) XEN_DOMCTL_gettscinfo or (2) XEN_SYSCTL_getdomaininfolist request (CVE-2015-3340).

The Floppy Disk Controller (FDC) in QEMU, as used in Xen 4.5.x and earlier and KVM, allows local guest users to cause a denial of service (out-of-bounds write and guest crash) or possibly execute arbitrary code via the (1) FD_CMD_READ_ID, (2) FD_CMD_DRIVE_SPECIFICATION_COMMAND, or other…

The XEN hypervisor received updates to fix various security issues and bugs.

The following security issues were fixed:

• CVE-2015-2151: XSA-123: A hypervisor memory corruption due to x86 emulator flaw.
• CVE-2015-2045: XSA-122: Information leak through version information hypercall.
• CVE-2015-2044: XSA-121: Information leak via internal x86 system device emulation.
• CVE-2015-2152: XSA-119: HVM qemu was unexpectedly enabling emulated VGA graphics backends.
• CVE-2014-3615: Information leakage when guest sets high graphics resolution.
• CVE-2015-0361: XSA-116: A xen crash due to use after free on hvm guest teardown.
• CVE-2014-9065, CVE-2014-9066: XSA-114: xen: p2m lock starvation.

Also the following bugs were fixed:

• bnc#919098 - XEN blktap device intermittently fails to connect
• bnc#882089 - Windows 2012 R2 fails to boot up with greater than 60 vcpus
• bnc#903680 - Problems with detecting free loop devices on Xen guest startup
• bnc#861318 - xentop reports 'Found interface vif101.0 but domain 101 does not exist.'
• Update seabios to rel-1.7.3.1 which is the correct version for Xen 4.4
• Enhancement to virsh/libvirtd 'send-key' command The xen side small fix. (FATE#317240)
• bnc#901488 - Intel ixgbe driver assigns rx/tx queues per core resulting in irq problems on servers with a large amount of CPU cores
• bnc#910254 - SLES11 SP3 Xen VT-d igb NIC doesn't work
• Add domain_migrate_constraints_set API to Xend's http interface (FATE#317239)
• Restore missing fixes from block-dmmd script
• bnc#904255 - XEN boot hangs in early boot on UEFI system
• bsc#912011 - high ping latency after upgrade to latest SLES11SP3 on xen Dom0
• Fix missing banner by restoring the figlet program.

The Virtualization service XEN was updated to fix various bugs and security issues.

The following security issues have been fixed:

* 

  CVE-2015-2756: XSA-126: Unmediated PCI command register access in
  qemu could have lead to denial of service attacks against the host,
  if PCI cards are - passed through to guests.

* 

  XSA-125: Long latency MMIO mapping operations were not preemptible.

* 

  CVE-2015-2151: XSA-123: Instructions with register operands ignored
  eventual segment overrides encoded for them. Due to an insufficiently
  conditional assignment such a bogus segment override could have,
  however, corrupted a pointer used subsequently to store the result of
  the instruction.

* 

  CVE-2015-2045: XSA-122: The code handling certain sub-operations of
  the HYPERVISOR_xen_version hypercall failed to fully initialize all
  fields of structures subsequently copied back to guest memory. Due to
  this hypervisor stack contents were copied into the destination of
  the operation, thus becoming visible to the guest.

* 

  CVE-2015-2044: XSA-121: Emulation routines in the hypervisor dealing
  with certain system devices checked whether the access size by the
  guest is a supported one. When the access size is unsupported these
  routines failed to set the data to be returned to the guest for read
  accesses, so that hypervisor stack contents were copied into the
  destination of the operation, thus becoming visible to the guest.

Security Issues:

* CVE-2015-2044
  <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2044>
* CVE-2015-2045
  <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2045>
* CVE-2015-2151
  <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2151>
* CVE-2015-2756
  <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2756>

The Virtualization service XEN was updated to fix various bugs and security issues.

The following security issues have been fixed:

* 

  CVE-2015-2756: XSA-126: Unmediated PCI command register access in
  qemu could have lead to denial of service attacks against the host,
  if PCI cards are passed through to guests.

* 

  XSA-125: Long latency MMIO mapping operations were not preemptible.

* 

  CVE-2015-2151: XSA-123: Instructions with register operands ignored
  eventual segment overrides encoded for them. Due to an insufficiently
  conditional assignment such a bogus segment override could have,
  however, corrupted a pointer used subsequently to store the result of
  the instruction.

* 

  CVE-2015-2045: XSA-122: The code handling certain sub-operations of
  the HYPERVISOR_xen_version hypercall failed to fully initialize all
  fields of structures subsequently copied back to guest memory. Due to
  this hypervisor stack contents were copied into the destination of
  the operation, thus becoming visible to the guest.

* 

  CVE-2015-2044: XSA-121: Emulation routines in the hypervisor dealing
  with certain system devices checked whether the access size by the
  guest is a supported one. When the access size is unsupported these
  routines failed to set the data to be returned to the guest for read
  accesses, so that hypervisor stack contents were copied into the
  destination of the operation, thus becoming visible to the guest.

Also fixed:

* Regular crashes of dom-0 on different servers due to races in MCE
  access were fixed. bsc#907755

Security Issues:

* CVE-2015-2044
  <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2044>
* CVE-2015-2045
  <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2045>
* CVE-2015-2151
  <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2151>
* CVE-2015-2756
  <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2756>

The Virtualization service XEN was updated to fix various bugs and security issues.

The following security issues have been fixed:

* 

  CVE-2015-2756: XSA-126: Unmediated PCI command register access in
  qemu could have lead to denial of service attacks against the host,
  if PCI cards are passed through to guests.

* 

  XSA-125: Long latency MMIO mapping operations were not preemptible.

* 

  CVE-2015-2151: XSA-123: Instructions with register operands ignored
  eventual segment overrides encoded for them. Due to an insufficiently
  conditional assignment such a bogus segment override could have,
  however, corrupted a pointer used subsequently to store the result of
  the instruction.

* 

  CVE-2015-2045: XSA-122: The code handling certain sub-operations of
  the HYPERVISOR_xen_version hypercall failed to fully initialize all
  fields of structures subsequently copied back to guest memory. Due to
  this hypervisor stack contents were copied into the destination of
  the operation, thus becoming visible to the guest.

* 

  CVE-2015-2044: XSA-121: Emulation routines in the hypervisor dealing
  with certain system devices checked whether the access size by the
  guest is a supported one. When the access size is unsupported these
  routines failed to set the data to be returned to the guest for read
  accesses, so that hypervisor stack contents were copied into the
  destination of the operation, thus becoming visible to the guest.

Also fixed:

* Fully virtualized guest install from network source failed with
  'cannot find guest domain' in XEN. (bsc#919341)

Security Issues:

* CVE-2015-2044
  <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2044>
* CVE-2015-2045
  <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2045>
* CVE-2015-2151
  <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2151>
* CVE-2015-2756
  <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2756>

The HYPERVISOR_xen_version hypercall in Xen 3.2.x through 4.5.x does not properly initialize data structures, which allows local guest users to obtain sensitive information via unspecified vectors.