Multiple integer overflows in the (1) FLASK_GETBOOL, (2) FLASK_SETBOOL, (3) FLASK_USER, and (4) FLASK_CONTEXT_TO_SID suboperations in the flask hypercall in Xen 4.3.x, 4.2.x, 4.1.x, 3.2.x, and earlier, when XSM is enabled, allow local users to cause a denial of service (processor fault) via unspecified vectors, a different vulnerability than CVE-2014-1892, CVE-2014-1893, and CVE-2014-1894.

The SUSE Linux Enterprise Server 11 Service Pack 1 LTSS Xen hypervisor and toolset have been updated to fix various security issues and some bugs.

The following security issues have been addressed :

XSA-84: CVE-2014-1894: Xen 3.2 (and presumably earlier) exhibit both problems with the overflow issue being present for more than just the suboperations listed above. (bnc#860163)

XSA-84: CVE-2014-1892 CVE-2014-1893: Xen 3.3 through 4.1, while not affected by the above overflow, have a different overflow issue on FLASK_{GET,SET}BOOL and expose unreasonably large memory allocation to arbitrary guests.
(bnc#860163)

XSA-84: CVE-2014-1891: The FLASK_{GET,SET}BOOL, FLASK_USER and FLASK_CONTEXT_TO_SID suboperations of the flask hypercall are vulnerable to an integer overflow on the input size. The hypercalls attempt to allocate a buffer which is 1 larger than this size and is therefore vulnerable to integer overflow and an attempt to allocate then access a zero byte buffer. (bnc#860163)

XSA-82: CVE-2013-6885: The microcode on AMD 16h 00h through 0Fh processors does not properly handle the interaction between locked instructions and write-combined memory types, which allows local users to cause a denial of service (system hang) via a crafted application, aka the errata 793 issue. (bnc#853049)

XSA-76: CVE-2013-4554: Xen 3.0.3 through 4.1.x (possibly 4.1.6.1), 4.2.x (possibly 4.2.3), and 4.3.x (possibly 4.3.1) does not properly prevent access to hypercalls, which allows local guest users to gain privileges via a crafted application running in ring 1 or 2. (bnc#849668)

XSA-74: CVE-2013-4553: The XEN_DOMCTL_getmemlist hypercall in Xen 3.4.x through 4.3.x (possibly 4.3.1) does not always obtain the page_alloc_lock and mm_rwlock in the same order, which allows local guest administrators to cause a denial of service (host deadlock). (bnc#849667)

XSA-73: CVE-2013-4494: Xen before 4.1.x, 4.2.x, and 4.3.x does not take the page_alloc_lock and grant_table.lock in the same order, which allows local guest administrators with access to multiple vcpus to cause a denial of service (host deadlock) via unspecified vectors. (bnc#848657)

XSA-67: CVE-2013-4368: The outs instruction emulation in Xen 3.1.x, 4.2.x, 4.3.x, and earlier, when using FS: or GS:
segment override, uses an uninitialized variable as a segment base, which allows local 64-bit PV guests to obtain sensitive information (hypervisor stack content) via unspecified vectors related to stale data in a segment register. (bnc#842511)

XSA-66: CVE-2013-4361: The fbld instruction emulation in Xen 3.3.x through 4.3.x does not use the correct variable for the source effective address, which allows local HVM guests to obtain hypervisor stack information by reading the values used by the instruction. (bnc#841766)

XSA-63: CVE-2013-4355: Xen 4.3.x and earlier does not properly handle certain errors, which allows local HVM guests to obtain hypervisor stack memory via a (1) port or (2) memory mapped I/O write or (3) other unspecified operations related to addresses without associated memory.
(bnc#840592)

XSA-62: CVE-2013-1442: Xen 4.0 through 4.3.x, when using AVX or LWP capable CPUs, does not properly clear previous data from registers when using an XSAVE or XRSTOR to extend the state components of a saved or restored vCPU after touching other restored extended registers, which allows local guest OSes to obtain sensitive information by reading the registers. (bnc#839596)

XSA-61: CVE-2013-4329: The xenlight library (libxl) in Xen 4.0.x through 4.2.x, when IOMMU is disabled, provides access to a busmastering-capable PCI passthrough device before the IOMMU setup is complete, which allows local HVM guest domains to gain privileges or cause a denial of service via a DMA instruction. (bnc#839618)

XSA-60: CVE-2013-2212: The vmx_set_uc_mode function in Xen 3.3 through 4.3, when disabling chaches, allows local HVM guests with access to memory mapped I/O regions to cause a denial of service (CPU consumption and possibly hypervisor or guest kernel panic) via a crafted GFN range. (bnc#831120)

XSA-58: CVE-2013-1918: Certain page table manipulation operations in Xen 4.1.x, 4.2.x, and earlier are not preemptible, which allows local PV kernels to cause a denial of service via vectors related to 'deep page table traversal.' (bnc#826882)

XSA-58: CVE-2013-1432: Xen 4.1.x and 4.2.x, when the XSA-45 patch is in place, does not properly maintain references on pages stored for deferred cleanup, which allows local PV guest kernels to cause a denial of service (premature page free and hypervisor crash) or possible gain privileges via unspecified vectors. (bnc#826882)

XSA-57: CVE-2013-2211: The libxenlight (libxl) toolstack library in Xen 4.0.x, 4.1.x, and 4.2.x uses weak permissions for xenstore keys for paravirtualised and emulated serial console devices, which allows local guest administrators to modify the xenstore value via unspecified vectors.
(bnc#823608)

XSA-56: CVE-2013-2072: Buffer overflow in the Python bindings for the xc_vcpu_setaffinity call in Xen 4.0.x, 4.1.x, and 4.2.x allows local administrators with permissions to configure VCPU affinity to cause a denial of service (memory corruption and xend toolstack crash) and possibly gain privileges via a crafted cpumap. (bnc#819416)

XSA-55: CVE-2013-2196: Multiple unspecified vulnerabilities in the Elf parser (libelf) in Xen 4.2.x and earlier allow local guest administrators with certain permissions to have an unspecified impact via a crafted kernel, related to 'other problems' that are not CVE-2013-2194 or CVE-2013-2195. (bnc#823011)

XSA-55: CVE-2013-2195: The Elf parser (libelf) in Xen 4.2.x and earlier allow local guest administrators with certain permissions to have an unspecified impact via a crafted kernel, related to 'pointer dereferences' involving unexpected calculations. (bnc#823011)

XSA-55: CVE-2013-2194: Multiple integer overflows in the Elf parser (libelf) in Xen 4.2.x and earlier allow local guest administrators with certain permissions to have an unspecified impact via a crafted kernel. (bnc#823011)

XSA-53: CVE-2013-2077: Xen 4.0.x, 4.1.x, and 4.2.x does not properly restrict the contents of a XRSTOR, which allows local PV guest users to cause a denial of service (unhandled exception and hypervisor crash) via unspecified vectors.
(bnc#820919)

XSA-52: CVE-2013-2076: Xen 4.0.x, 4.1.x, and 4.2.x, when running on AMD64 processors, only save/restore the FOP, FIP, and FDP x87 registers in FXSAVE/FXRSTOR when an exception is pending, which allows one domain to determine portions of the state of floating point instructions of other domains, which can be leveraged to obtain sensitive information such as cryptographic keys, a similar vulnerability to CVE-2006-1056. NOTE: this is the documented behavior of AMD64 processors, but it is inconsistent with Intel processors in a security-relevant fashion that was not addressed by the kernels. (bnc#820917)

XSA-50: CVE-2013-1964: Xen 4.0.x and 4.1.x incorrectly releases a grant reference when releasing a non-v1, non-transitive grant, which allows local guest administrators to cause a denial of service (host crash), obtain sensitive information, or possible have other impacts via unspecified vectors. (bnc#816156)

XSA-49: CVE-2013-1952: Xen 4.x, when using Intel VT-d for a bus mastering capable PCI device, does not properly check the source when accessing a bridge device's interrupt remapping table entries for MSI interrupts, which allows local guest domains to cause a denial of service (interrupt injection) via unspecified vectors. (bnc#816163)

XSA-47: CVE-2013-1920: Xen 4.2.x, 4.1.x, and earlier, when the hypervisor is running 'under memory pressure' and the Xen Security Module (XSM) is enabled, uses the wrong ordering of operations when extending the per-domain event channel tracking table, which causes a use-after-free and allows local guest kernels to inject arbitrary events and gain privileges via unspecified vectors. (bnc#813677)

XSA-46: CVE-2013-1919: Xen 4.2.x and 4.1.x does not properly restrict access to IRQs, which allows local stub domain clients to gain access to IRQs and cause a denial of service via vectors related to 'passed-through IRQs or PCI devices.' (bnc#813675)

XSA-45: CVE-2013-1918: Certain page table manipulation operations in Xen 4.1.x, 4.2.x, and earlier are not preemptible, which allows local PV kernels to cause a denial of service via vectors related to 'deep page table traversal.' (bnc#816159)

XSA-44: CVE-2013-1917: Xen 3.1 through 4.x, when running 64-bit hosts on Intel CPUs, does not clear the NT flag when using an IRET after a SYSENTER instruction, which allows PV guest users to cause a denial of service (hypervisor crash) by triggering a #GP fault, which is not properly handled by another IRET instruction. (bnc#813673)

XSA-41: CVE-2012-6075: Buffer overflow in the e1000_receive function in the e1000 device driver (hw/e1000.c) in QEMU 1.3.0-rc2 and other versions, when the SBP and LPE flags are disabled, allows remote attackers to cause a denial of service (guest OS crash) and possibly execute arbitrary guest code via a large packet. (bnc#797523)

XSA-37: CVE-2013-0154: The get_page_type function in xen/arch/x86/mm.c in Xen 4.2, when debugging is enabled, allows local PV or HVM guest administrators to cause a denial of service (assertion failure and hypervisor crash) via unspecified vectors related to a hypercall. (bnc#797031)

XSA-36: CVE-2013-0153: The AMD IOMMU support in Xen 4.2.x, 4.1.x, 3.3, and other versions, when using AMD-Vi for PCI passthrough, uses the same interrupt remapping table for the host and all guests, which allows guests to cause a denial of service by injecting an interrupt into other guests.
(bnc#800275)

XSA-33: CVE-2012-5634: Xen 4.2.x, 4.1.x, and 4.0, when using Intel VT-d for PCI passthrough, does not properly configure VT-d when supporting a device that is behind a legacy PCI Bridge, which allows local guests to cause a denial of service to other guests by injecting an interrupt.
(bnc#794316)

XSA-31: CVE-2012-5515: The (1) XENMEM_decrease_reservation, (2) XENMEM_populate_physmap, and (3) XENMEM_exchange hypercalls in Xen 4.2 and earlier allow local guest administrators to cause a denial of service (long loop and hang) via a crafted extent_order value. (bnc#789950)

XSA-30: CVE-2012-5514: The guest_physmap_mark_populate_on_demand function in Xen 4.2 and earlier does not properly unlock the subject GFNs when checking if they are in use, which allows local guest HVM administrators to cause a denial of service (hang) via unspecified vectors. (bnc#789948)

XSA-29: CVE-2012-5513: The XENMEM_exchange handler in Xen 4.2 and earlier does not properly check the memory address, which allows local PV guest OS administrators to cause a denial of service (crash) or possibly gain privileges via unspecified vectors that overwrite memory in the hypervisor reserved range. (bnc#789951)

XSA-27: CVE-2012-6333: Multiple HVM control operations in Xen 3.4 through 4.2 allow local HVM guest OS administrators to cause a denial of service (physical CPU consumption) via a large input. (bnc#789944)

XSA-27: CVE-2012-5511: Stack-based buffer overflow in the dirty video RAM tracking functionality in Xen 3.4 through 4.1 allows local HVM guest OS administrators to cause a denial of service (crash) via a large bitmap image.
(bnc#789944)

XSA-26: CVE-2012-5510: Xen 4.x, when downgrading the grant table version, does not properly remove the status page from the tracking list when freeing the page, which allows local guest OS administrators to cause a denial of service (hypervisor crash) via unspecified vectors. (bnc#789945)

XSA-25: CVE-2012-4544: The PV domain builder in Xen 4.2 and earlier does not validate the size of the kernel or ramdisk (1) before or (2) after decompression, which allows local guest administrators to cause a denial of service (domain 0 memory consumption) via a crafted (a) kernel or (b) ramdisk.
(bnc#787163)

XSA-24: CVE-2012-4539: Xen 4.0 through 4.2, when running 32-bit x86 PV guests on 64-bit hypervisors, allows local guest OS administrators to cause a denial of service (infinite loop and hang or crash) via invalid arguments to GNTTABOP_get_status_frames, aka 'Grant table hypercall infinite loop DoS vulnerability.' (bnc#786520)

XSA-23: CVE-2012-4538: The HVMOP_pagetable_dying hypercall in Xen 4.0, 4.1, and 4.2 does not properly check the pagetable state when running on shadow pagetables, which allows a local HVM guest OS to cause a denial of service (hypervisor crash) via unspecified vectors. (bnc#786519)

XSA-22: CVE-2012-4537: Xen 3.4 through 4.2, and possibly earlier versions, does not properly synchronize the p2m and m2p tables when the set_p2m_entry function fails, which allows local HVM guest OS administrators to cause a denial of service (memory consumption and assertion failure), aka 'Memory mapping failure DoS vulnerability.' (bnc#786517)

XSA-20: CVE-2012-4535: Xen 3.4 through 4.2, and possibly earlier versions, allows local guest OS administrators to cause a denial of service (Xen infinite loop and physical CPU consumption) by setting a VCPU with an 'inappropriate deadline.' (bnc#786516)

XSA-19: CVE-2012-4411: The graphical console in Xen 4.0, 4.1 and 4.2 allows local OS guest administrators to obtain sensitive host resource information via the qemu monitor.
NOTE: this might be a duplicate of CVE-2007-0998.
(bnc#779212)

XSA-15: CVE-2012-3497: (1) TMEMC_SAVE_GET_CLIENT_WEIGHT, (2) TMEMC_SAVE_GET_CLIENT_CAP, (3) TMEMC_SAVE_GET_CLIENT_FLAGS and (4) TMEMC_SAVE_END in the Transcendent Memory (TMEM) in Xen 4.0, 4.1, and 4.2 allow local guest OS users to cause a denial of service (NULL pointer dereference or memory corruption and host crash) or possibly have other unspecified impacts via a NULL client id. (bnc#777890)

Also the following non-security bugs have been fixed :

  - xen hot plug attach/detach fails modified     blktap-pv-cdrom.patch. (bnc#805094)

  - guest 'disappears' after live migration Updated     block-dmmd script. (bnc#777628)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The SUSE Linux Enterprise Server 11 Service Pack 2 LTSS Xen hypervisor and toolset has been updated to fix various security issues and several bugs.

The following security issues have been addressed :

XSA-88: CVE-2014-1950: Use-after-free vulnerability in the xc_cpupool_getinfo function in Xen 4.1.x through 4.3.x, when using a multithreaded toolstack, does not properly handle a failure by the xc_cpumap_alloc function, which allows local users with access to management functions to cause a denial of service (heap corruption) and possibly gain privileges via unspecified vectors. (bnc#861256)

XSA-87: CVE-2014-1666: The do_physdev_op function in Xen 4.1.5, 4.1.6.1, 4.2.2 through 4.2.3, and 4.3.x does not properly restrict access to the (1) PHYSDEVOP_prepare_msix and (2) PHYSDEVOP_release_msix operations, which allows local PV guests to cause a denial of service (host or guest malfunction) or possibly gain privileges via unspecified vectors. (bnc#860302)

XSA-84: CVE-2014-1894: Xen 3.2 (and presumably earlier) exhibit both problems with the overflow issue being present for more than just the suboperations listed above.
(bnc#860163)

XSA-84: CVE-2014-1892 CVE-2014-1893: Xen 3.3 through 4.1, while not affected by the above overflow, have a different overflow issue on FLASK_{GET,SET}BOOL and expose unreasonably large memory allocation to arbitrary guests.
(bnc#860163)

XSA-84: CVE-2014-1891: The FLASK_{GET,SET}BOOL, FLASK_USER and FLASK_CONTEXT_TO_SID suboperations of the flask hypercall are vulnerable to an integer overflow on the input size. The hypercalls attempt to allocate a buffer which is 1 larger than this size and is therefore vulnerable to integer overflow and an attempt to allocate then access a zero byte buffer. (bnc#860163)

XSA-82: CVE-2013-6885: The microcode on AMD 16h 00h through 0Fh processors does not properly handle the interaction between locked instructions and write-combined memory types, which allows local users to cause a denial of service (system hang) via a crafted application, aka the errata 793 issue. (bnc#853049)

XSA-76: CVE-2013-4554: Xen 3.0.3 through 4.1.x (possibly 4.1.6.1), 4.2.x (possibly 4.2.3), and 4.3.x (possibly 4.3.1) does not properly prevent access to hypercalls, which allows local guest users to gain privileges via a crafted application running in ring 1 or 2. (bnc#849668)

XSA-74: CVE-2013-4553: The XEN_DOMCTL_getmemlist hypercall in Xen 3.4.x through 4.3.x (possibly 4.3.1) does not always obtain the page_alloc_lock and mm_rwlock in the same order, which allows local guest administrators to cause a denial of service (host deadlock). (bnc#849667)

XSA-60: CVE-2013-2212: The vmx_set_uc_mode function in Xen 3.3 through 4.3, when disabling chaches, allows local HVM guests with access to memory mapped I/O regions to cause a denial of service (CPU consumption and possibly hypervisor or guest kernel panic) via a crafted GFN range. (bnc#831120)

Also the following non-security bugs have been fixed :

  - Boot Failure with xen kernel in UEFI mode with error 'No     memory for trampoline' (bnc#833483)

  - Fixed Xen hypervisor panic on 8-blades nPar with 46-bit     memory addressing. (bnc#848014)

  - In HP's UEFI x86_64 platform and sles11sp3 with xen     environment, dom0 will soft lockup on multiple blades     nPar. (bnc#842417)

  - Soft lockup with PCI passthrough and many VCPUs     (bnc#846849)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote host is affected by the vulnerability described in GLSA-201407-03 (Xen: Multiple Vunlerabilities)

    Multiple vulnerabilities have been discovered in Xen. Please review the       CVE identifiers referenced below for details.
  Impact :

    A remote attacker can utilize multiple vectors to execute arbitrary       code, cause Denial of Service, or gain access to data on the host.
  Workaround :

    There is no known workaround at this time.

Xen was updated to fix various bugs and security issues :

Update to Xen version 4.2.4 c/s 26280.

  - bnc#861256 - CVE-2014-1950: xen: XSA-88: use-after-free     in xc_cpupool_getinfo() under memory pressure. (fix     included with update)

  - bnc#863297: xend/pvscsi: recognize also SCSI CDROM     devices

  - bnc#858496 - CVE-2014-1642: Xen: XSA-83: Out-of-memory     condition yielding memory corruption during IRQ setup

  - bnc#860163 - xen: XSA-84: integer overflow in several     XSM/Flask hypercalls (CVE-2014-1891 CVE-2014-1892     CVE-2014-1893 CVE-2014-1894)

  - bnc#860165 - CVE-2014-1895: xen: XSA-85: Off-by-one     error in FLASK_AVC_CACHESTAT hypercall

  - bnc#860300 - CVE-2014-1896: xen: XSA-86: libvchan     failure handling malicious ring indexes

  - bnc#860302 - CVE-2014-1666: xen: XSA-87:
    PHYSDEVOP_(prepare,release)_msix exposed to unprivileged     guests

  - bnc#858311 - Server is not booting in kernel XEN after     latest updates - (XEN) setup 0000:00:18.0 for d0 failed     (-19)

  - bnc#858496 - CVE-2014-1642: Xen: XSA-83: Out-of-memory     condition yielding memory corruption during IRQ setup

  - bnc#853049 - CVE-2013-6885: xen: XSA-82: Guest     triggerable AMD CPU erratum may cause host hang

  - bnc#853048 - CVE-2013-6400: xen: XSA-80: IOMMU TLB     flushing may be inadvertently suppressed

  - bnc#831120 - CVE-2013-2212: xen: XSA-60: Excessive time     to disable caching with HVM guests with PCI passthrough

  - bnc#848014 - [HP HPS] Xen hypervisor panics on 8-blades     nPar with 46-bit memory addressing

  - bnc#833251 - [HP BCS SLES11 Bug]: In HPs UEFI x86_64     platform and with xen environment, in booting stage ,xen     hypervisor will panic.

  - pygrub: Support (/dev/xvda) style disk specifications

  - bnc#849667 - CVE-2014-1895: xen: XSA-74: Lock order     reversal between page_alloc_lock and mm_rwlock

  - bnc#849668 - CVE-2013-4554: xen: XSA-76: Hypercalls     exposed to privilege rings 1 and 2 of HVM guests

  - bnc#842417 - In HPs UEFI x86_64 platform and sles11sp3     with xen environment, dom0 will soft lockup on multiple     blades nPar.

  - bnc#848014 - [HP HPS] Xen hypervisor panics on 8-blades     nPar with 46-bit memory addressing

  - bnc#846849 - Soft lockup with PCI passthrough and many     VCPUs

  - bnc#833483 - Boot Failure with xen kernel in UEFI mode     with error 'No memory for trampoline'

  - bnc#849665 - CVE-2013-4551: xen: XSA-75: Host crash due     to guest VMX instruction execution

  - The upstream version of checking for xend when using the     'xl' command is used is not working.

  - bnc#840997 - It is possible to start a VM twice on the     same node.

  - bnc#848657 - xen: CVE-2013-4494: XSA-73: Lock order     reversal between page allocation and grant table locks

The SUSE Linux Enterprise Server 11 Service Pack 3 Xen hypervisor and toolset has been updated to 4.2.4 to fix various bugs and security issues :

The following security issues have been addressed :

  - XSA-60: CVE-2013-2212: The vmx_set_uc_mode function in     Xen 3.3 through 4.3, when disabling chaches, allows     local HVM guests with access to memory mapped I/O     regions to cause a denial of service (CPU consumption     and possibly hypervisor or guest kernel panic) via a     crafted GFN range. (bnc#831120)

  - XSA-80: CVE-2013-6400: Xen 4.2.x and 4.3.x, when using     Intel VT-d and a PCI device has been assigned, does not     clear the flag that suppresses IOMMU TLB flushes when     unspecified errors occur, which causes the TLB entries     to not be flushed and allows local guest administrators     to cause a denial of service (host crash) or gain     privileges via unspecified vectors. (bnc#853048)

  - XSA-82: CVE-2013-6885: The microcode on AMD 16h 00h     through 0Fh processors does not properly handle the     interaction between locked instructions and     write-combined memory types, which allows local users to     cause a denial of service (system hang) via a crafted     application, aka the errata 793 issue. (bnc#853049)

  - XSA-83: CVE-2014-1642: The IRQ setup in Xen 4.2.x and     4.3.x, when using device passthrough and configured to     support a large number of CPUs, frees certain memory     that may still be intended for use, which allows local     guest administrators to cause a denial of service     (memory corruption and hypervisor crash) and possibly     execute arbitrary code via vectors related to an     out-of-memory error that triggers a (1) use-after-free     or (2) double free. (bnc#860092)

  - XSA-84: CVE-2014-1891: The FLASK_{GET,SET}BOOL,     FLASK_USER and FLASK_CONTEXT_TO_SID suboperations of the     flask hypercall are vulnerable to an integer overflow on     the input size. The hypercalls attempt to allocate a     buffer which is 1 larger than this size and is therefore     vulnerable to integer overflow and an attempt to     allocate then access a zero byte buffer. (bnc#860163)

  - XSA-84: CVE-2014-1892 / CVE-2014-1893: Xen 3.3 through     4.1, while not affected by the above overflow, have a     different overflow issue on FLASK_{GET,SET}BOOL and     expose unreasonably large memory allocation to     aribitrary guests. (bnc#860163)

  - XSA-84: CVE-2014-1894: Xen 3.2 (and presumably earlier)     exhibit both problems with the overflow issue being     present for more than just the suboperations listed     above. (bnc#860163)

  - XSA-85: CVE-2014-1895: The FLASK_AVC_CACHESTAT     hypercall, which provides access to per-cpu statistics     on the Flask security policy, incorrectly validates the     CPU for which statistics are being requested.
    (bnc#860165)

  - XSA-86: CVE-2014-1896: libvchan (a library for     inter-domain communication) does not correctly handle     unusual or malicious contents in the xenstore ring. A     malicious guest can exploit this to cause a     libvchan-using facility to read or write past the end of     the ring. (bnc#860300)

  - XSA-87: CVE-2014-1666: The do_physdev_op function in Xen     4.1.5, 4.1.6.1, 4.2.2 through 4.2.3, and 4.3.x does not     properly restrict access to the (1)     PHYSDEVOP_prepare_msix and (2) PHYSDEVOP_release_msix     operations, which allows local PV guests to cause a     denial of service (host or guest malfunction) or     possibly gain privileges via unspecified vectors.
    (bnc#860302)

  - XSA-88: CVE-2014-1950: Use-after-free vulnerability in     the xc_cpupool_getinfo function in Xen 4.1.x through     4.3.x, when using a multithreaded toolstack, does not     properly handle a failure by the xc_cpumap_alloc     function, which allows local users with access to     management functions to cause a denial of service (heap     corruption) and possibly gain privileges via unspecified     vectors. (bnc#861256)

Also the following non-security bugs have been fixed :

  - Fixed boot problems with Xen kernel. '(XEN) setup     0000:00:18.0 for d0 failed (-19)'. (bnc#858311)

  - Fixed Xen hypervisor panic on 8-blades nPar with 46-bit     memory addressing. (bnc#848014)

  - Fixed Xen hypervisor panic in HP's UEFI x86_64 platform     and with xen environment, in booting stage. (bnc#833251)

  - xend/pvscsi: recognize also SCSI CDROM devices.
    (bnc#863297)

  - pygrub: Support (/dev/xvda) style disk specifications

three security fixes: integer overflow in several XSM/Flask hypercalls [XSA-84] Off-by-one error in FLASK_AVC_CACHESTAT hypercall [XSA-85] libvchan failure handling malicious ring indexes [XSA-86]

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

three security fixes: integer overflow in several XSM/Flask hypercalls [XSA-84], Off-by-one error in FLASK_AVC_CACHESTAT hypercall [XSA-85], libvchan failure handling malicious ring indexes [XSA-86]

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
83616	SUSE SLES11 Security Update : Xen (SUSE-SU-2014:0446-1)	Nessus	SuSE Local Security Checks	high
83613	SUSE SLES11 Security Update : Xen (SUSE-SU-2014:0372-1)	Nessus	SuSE Local Security Checks	high
76544	GLSA-201407-03 : Xen: Multiple Vunlerabilities	Nessus	Gentoo Local Security Checks	high
75312	openSUSE Security Update : xen (openSUSE-SU-2014:0483-1)	Nessus	SuSE Local Security Checks	high
73015	SuSE 11.3 Security Update : Xen (SAT Patch Number 8973)	Nessus	SuSE Local Security Checks	high
72540	Fedora 19 : xen-4.2.3-15.fc19 (2014-2188)	Nessus	Fedora Local Security Checks	medium
72539	Fedora 20 : xen-4.3.1-9.fc20 (2014-2170)	Nessus	Fedora Local Security Checks	medium

Detections

Analytics

CVE-2014-1891

high

Tenable Plugins

high

high

high

high

high

medium

medium