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.

The remote OracleVM system is missing necessary patches to address critical security updates : please see Oracle VM Security Advisory OVMSA-2015-0068 for details.

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 remote OracleVM system is missing necessary patches to address critical security updates :

  - oxenstored incorrect handling of certain Xenbus ring     states Xen Security Advisory 38 (CVE-2013-0215) Patch     xsa38.patch The oxenstored daemon (the ocaml version of     the xenstore daemon) does not correctly handle unusual     or malicious contents in the xenstore ring. A malicious     guest can exploit this to cause oxenstored to read past     the end of the ring (and very likely crash) or to     allocate large amounts of RAM. Signed-off-by Chuck     Anderson (CVE-2013-0215)

  - ACPI: acpi_table_parse should return handler's error     code Currently, the error code returned by     acpi_table_parse's handler is ignored. This patch will     propagate handler's return value to acpi_table_parse's     caller. AMD,IOMMU: Clean up old entries in remapping     tables when creating new interrupt mapping. When     changing the affinity of an IRQ associated with a passed     through PCI device, clear previous mapping. In addition,     because some BIOSes may incorrectly program IVRS entries     for IOAPIC try to check for entry's consistency.
    Specifically, if conflicting entries are found disable     IOMMU if per-device remapping table is used. If entries     refer to bogus IOAPIC IDs disable IOMMU unconditionally     AMD,IOMMU: Disable IOMMU if SATA Combined mode is on     AMD's SP5100 chipset can be placed into SATA Combined     mode that may cause prevent dom0 from booting when IOMMU     is enabled and per-device interrupt remapping table is     used. While SP5100 erratum 28 requires BIOSes to disable     this mode, some may still use it. This patch checks     whether this mode is on and, if per-device table is in     use, disables IOMMU. AMD,IOMMU: Make per-device     interrupt remapping table default Using global interrupt     remapping table may be insecure, as described by XSA-36.
    This patch makes per-device mode default. This is XSA-36     / CVE-2013-0153. (CVE-2013-0153)

XEN was updated to fix various bugs and security issues :

Security issues fixed :

  - bnc#800275 - CVE-2013-0153: xen: interrupt remap entries     shared and old ones not cleared on AMD IOMMUs

  - bnc#797523 - CVE-2012-6075: qemu / kvm-qemu: e1000     overflows under some conditions

  - bnc#797031 - Xen Security Advisory 37 (CVE-2013-0154) -     Hypervisor crash due to incorrect ASSERT (debug build     only)

  - bnc#794316 - CVE-2012-5634: xen: VT-d interrupt     remapping source validation flaw (XSA-33)

Bugs fixed :

  - Upstream patches from Jan 26536-xenoprof-div-by-0.patch     26578-AMD-IOMMU-replace-BUG_ON.patch     26656-x86-fix-null-pointer-dereference-in-intel_get_exte     nded_msrs.patch     26659-AMD-IOMMU-erratum-746-workaround.patch     26660-x86-fix-CMCI-injection.patch     26672-vmx-fix-handling-of-NMI-VMEXIT.patch     26673-Avoid-stale-pointer-when-moving-domain-to-another-     cpupool.patch     26676-fix-compat-memory-exchange-op-splitting.patch     26677-x86-make-certain-memory-sub-ops-return-valid-value     s.patch 26678-SEDF-avoid-gathering-vCPU-s-on-pCPU0.patch     26679-x86-defer-processing-events-on-the-NMI-exit-path.p     atch     26683-credit1-Use-atomic-bit-operations-for-the-flags-st     ructure.patch     26692-x86-MSI-fully-protect-MSI-X-table.patch

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

  - bnc#802690 - domain locking can prevent a live migration     from completing modified xend-domain-lock.patch

  - bnc#797014 - no way to control live migrations     26547-tools-xc_fix_logic_error_in_stdiostream_progress.p     atch     26548-tools-xc_handle_tty_output_differently_in_stdiostr     eam_progress.patch     26549-tools-xc_turn_XCFLAGS__into_shifts.patch     26550-tools-xc_restore_logging_in_xc_save.patch     26551-tools-xc_log_pid_in_xc_save-xc_restore_output.patc     h     26675-tools-xentoollog_update_tty_detection_in_stdiostre     am_progress.patch     xen.migrate.tools-xc_print_messages_from_xc_save_with_xc
    _report.patch     xen.migrate.tools-xc_document_printf_calls_in_xc_restore     .patch     xen.migrate.tools-xc_rework_xc_save.cswitch_qemu_logdirt     y.patch     xen.migrate.tools_set_migration_constraints_from_cmdline     .patch     xen.migrate.tools_add_xm_migrate_--log_progress_option.p     atch

  - remove old patches: xen.xc.progress.patch     xen.xc_save.details.patch     xen.migration.abort_if_busy.patch

  - bnc#806736: enabling xentrace crashes hypervisor     26686-xentrace_fix_off-by-one_in_calculate_tbuf_size.pat     ch

  - Upstream patches from Jan     26287-sched-credit-pick-idle.patch     26501-VMX-simplify-CR0-update.patch     26502-VMX-disable-SMEP-when-not-paging.patch     26516-ACPI-parse-table-retval.patch (Replaces     CVE-2013-0153-xsa36.patch)     26517-AMD-IOMMU-clear-irtes.patch (Replaces     CVE-2013-0153-xsa36.patch)     26518-AMD-IOMMU-disable-if-SATA-combined-mode.patch     (Replaces CVE-2013-0153-xsa36.patch)     26519-AMD-IOMMU-perdev-intremap-default.patch (Replaces     CVE-2013-0153-xsa36.patch) 26526-pvdrv-no-devinit.patch     26531-AMD-IOMMU-IVHD-special-missing.patch (Replaces     CVE-2013-0153-xsa36.patch)

  - bnc#798188 - Add $network to xend initscript     dependencies

  - bnc#797014 - no way to control live migrations

  - fix logic error in stdiostream_progress     xen.xc.progress.patch

  - restore logging in xc_save xen.xc_save.details.patch

  - add options to control migration tunables

    --max_iters, --max_factor, --abort_if_busy     xen.migration.abort_if_busy.patch

  - bnc#799694 - Unable to dvd or cdrom-boot DomU after     xen-tools update Fixed with update to Xen version 4.1.4

  - bnc#800156 - L3: HP iLo Generate NMI function not     working in XEN kernel 26440-x86-forward-SERR.patch

  - Upstream patches from Jan     26404-x86-forward-both-NMI-kinds.patch     26427-x86-AMD-enable-WC+.patch 

  - bnc#793927 - Xen VMs with more than 2 disks randomly     fail to start 25590-hotplug-locking.patch     25595-hotplug-locking.patch 26079-hotplug-locking.patch

  - Upstream patches from Jan     26332-x86-compat-show-guest-stack-mfn.patch     26333-x86-get_page_type-assert.patch (Replaces     CVE-2013-0154-xsa37.patch)     26340-VT-d-intremap-verify-legacy-bridge.patch (Replaces     CVE-2012-5634-xsa33.patch)     26370-libxc-x86-initial-mapping-fit.patch

  - Update to Xen 4.1.4 c/s 23432

  - Update xenpaging.guest-memusage.patch add rule for     xenmem to avoid spurious build failures

  - Upstream patches from Jan 26179-PCI-find-next-cap.patch     26183-x86-HPET-masking.patch     26188-x86-time-scale-asm.patch     26200-IOMMU-debug-verbose.patch     26203-x86-HAP-dirty-vram-leak.patch     26229-gnttab-version-switch.patch (Replaces     CVE-2012-5510-xsa26.patch)     26230-x86-HVM-limit-batches.patch (Replaces     CVE-2012-5511-xsa27.patch)     26231-memory-exchange-checks.patch (Replaces     CVE-2012-5513-xsa29.patch)     26232-x86-mark-PoD-error-path.patch (Replaces     CVE-2012-5514-xsa30.patch)     26233-memop-order-checks.patch (Replaces     CVE-2012-5515-xsa31.patch)     26235-IOMMU-ATS-max-queue-depth.patch     26272-x86-EFI-makefile-cflags-filter.patch     26294-x86-AMD-Fam15-way-access-filter.patch     CVE-2013-0154-xsa37.patch

  - Restore c/s 25751 in 23614-x86_64-EFI-boot.patch. Modify     the EFI Makefile to do additional filtering.
    EFI-makefile-cflags-filter.patch

XEN was updated to fix various bugs and security issues :

Security issues fixed :

  - bnc#800275 - CVE-2013-0153: xen: interrupt remap entries     shared and old ones not cleared on AMD IOMMUs

  - bnc#797523 - CVE-2012-6075: qemu / kvm-qemu: e1000     overflows under some conditions

  - bnc#797031 - Xen Security Advisory 37 (CVE-2013-0154) -     Hypervisor crash due to incorrect ASSERT (debug build     only)

  - bnc#794316 - CVE-2012-5634: xen: VT-d interrupt     remapping source validation flaw (XSA-33) 

Bugs fixed :

  - Upstream patches from Jan 26536-xenoprof-div-by-0.patch     26578-AMD-IOMMU-replace-BUG_ON.patch     26656-x86-fix-null-pointer-dereference-in-intel_get_exte     nded_msrs.patch     26659-AMD-IOMMU-erratum-746-workaround.patch     26660-x86-fix-CMCI-injection.patch     26672-vmx-fix-handling-of-NMI-VMEXIT.patch     26673-Avoid-stale-pointer-when-moving-domain-to-another-     cpupool.patch     26676-fix-compat-memory-exchange-op-splitting.patch     26677-x86-make-certain-memory-sub-ops-return-valid-value     s.patch 26678-SEDF-avoid-gathering-vCPU-s-on-pCPU0.patch     26679-x86-defer-processing-events-on-the-NMI-exit-path.p     atch     26683-credit1-Use-atomic-bit-operations-for-the-flags-st     ructure.patch     26692-x86-MSI-fully-protect-MSI-X-table.patch

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

  - bnc#802690 - domain locking can prevent a live migration     from completing modified xend-domain-lock.patch

  - bnc#797014 - no way to control live migrations     26547-tools-xc_fix_logic_error_in_stdiostream_progress.p     atch     26548-tools-xc_handle_tty_output_differently_in_stdiostr     eam_progress.patch     26549-tools-xc_turn_XCFLAGS__into_shifts.patch     26550-tools-xc_restore_logging_in_xc_save.patch     26551-tools-xc_log_pid_in_xc_save-xc_restore_output.patc     h     26675-tools-xentoollog_update_tty_detection_in_stdiostre     am_progress.patch     xen.migrate.tools-xc_print_messages_from_xc_save_with_xc
    _report.patch     xen.migrate.tools-xc_document_printf_calls_in_xc_restore     .patch     xen.migrate.tools-xc_rework_xc_save.cswitch_qemu_logdirt     y.patch     xen.migrate.tools_set_migration_constraints_from_cmdline     .patch     xen.migrate.tools_add_xm_migrate_--log_progress_option.p     atch

  - remove old patches: xen.xc.progress.patch     xen.xc_save.details.patch     xen.migration.abort_if_busy.patch

  - bnc#806736: enabling xentrace crashes hypervisor     26686-xentrace_fix_off-by-one_in_calculate_tbuf_size.pat     ch

  - Upstream patches from Jan     26287-sched-credit-pick-idle.patch     26501-VMX-simplify-CR0-update.patch     26502-VMX-disable-SMEP-when-not-paging.patch     26516-ACPI-parse-table-retval.patch (Replaces     CVE-2013-0153-xsa36.patch)     26517-AMD-IOMMU-clear-irtes.patch (Replaces     CVE-2013-0153-xsa36.patch)     26518-AMD-IOMMU-disable-if-SATA-combined-mode.patch     (Replaces CVE-2013-0153-xsa36.patch)     26519-AMD-IOMMU-perdev-intremap-default.patch (Replaces     CVE-2013-0153-xsa36.patch) 26526-pvdrv-no-devinit.patch     26531-AMD-IOMMU-IVHD-special-missing.patch (Replaces     CVE-2013-0153-xsa36.patch)

  - bnc#798188 - Add $network to xend initscript     dependencies

  - bnc#797014 - no way to control live migrations

  - fix logic error in stdiostream_progress     xen.xc.progress.patch

  - restore logging in xc_save xen.xc_save.details.patch

  - add options to control migration tunables

    --max_iters, --max_factor, --abort_if_busy     xen.migration.abort_if_busy.patch

  - bnc#799694 - Unable to dvd or cdrom-boot DomU after     xen-tools update Fixed with update to Xen version 4.1.4

  - bnc#800156 - L3: HP iLo Generate NMI function not     working in XEN kernel 26440-x86-forward-SERR.patch

  - Upstream patches from Jan     26404-x86-forward-both-NMI-kinds.patch     26427-x86-AMD-enable-WC+.patch

  - bnc#793927 - Xen VMs with more than 2 disks randomly     fail to start 25590-hotplug-locking.patch     25595-hotplug-locking.patch 26079-hotplug-locking.patch

  - Upstream patches from Jan     26332-x86-compat-show-guest-stack-mfn.patch     26333-x86-get_page_type-assert.patch (Replaces     CVE-2013-0154-xsa37.patch)     26340-VT-d-intremap-verify-legacy-bridge.patch (Replaces     CVE-2012-5634-xsa33.patch)     26370-libxc-x86-initial-mapping-fit.patch

  - Update to Xen 4.1.4 c/s 23432 

  - Update xenpaging.guest-memusage.patch add rule for     xenmem to avoid spurious build failures

  - Upstream patches from Jan 26179-PCI-find-next-cap.patch     26183-x86-HPET-masking.patch     26188-x86-time-scale-asm.patch     26200-IOMMU-debug-verbose.patch     26203-x86-HAP-dirty-vram-leak.patch     26229-gnttab-version-switch.patch (Replaces     CVE-2012-5510-xsa26.patch)     26230-x86-HVM-limit-batches.patch (Replaces     CVE-2012-5511-xsa27.patch)     26231-memory-exchange-checks.patch (Replaces     CVE-2012-5513-xsa29.patch)     26232-x86-mark-PoD-error-path.patch (Replaces     CVE-2012-5514-xsa30.patch)     26233-memop-order-checks.patch (Replaces     CVE-2012-5515-xsa31.patch)     26235-IOMMU-ATS-max-queue-depth.patch     26272-x86-EFI-makefile-cflags-filter.patch     26294-x86-AMD-Fam15-way-access-filter.patch     CVE-2013-0154-xsa37.patch

  - Restore c/s 25751 in 23614-x86_64-EFI-boot.patch. Modify     the EFI Makefile to do additional filtering.
    EFI-makefile-cflags-filter.patch

The remote host is affected by the vulnerability described in GLSA-201309-24 (Xen: Multiple vulnerabilities)

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

    Guest domains could possibly gain privileges, execute arbitrary code, or       cause a Denial of Service on the host domain (Dom0). Additionally, guest       domains could gain information about other virtual machines running on       the same host or read arbitrary files on the host.
  Workaround :

    The CVEs listed below do not currently have fixes, but only apply to Xen       setups which have &ldquo;tmem&rdquo; specified on the hypervisor command line.
      TMEM is not currently supported for use in production systems, and       administrators using tmem should disable it.
      Relevant CVEs:
      * CVE-2012-2497
      * CVE-2012-6030
      * CVE-2012-6031
      * CVE-2012-6032
      * CVE-2012-6033
      * CVE-2012-6034
      * CVE-2012-6035
      * CVE-2012-6036

The remote Oracle Linux 5 host has packages installed that are affected by a vulnerability as referenced in the ELSA-2013-0847 advisory.

    - [xen] AMD IOMMU: spot missing IO-APIC entries in IVRS table (Igor Mammedov) [910912 910913]     {CVE-2013-0153}
    - [xen] AMD, IOMMU: Make per-device interrupt remap table default (Igor Mammedov) [910912 910913]     {CVE-2013-0153}
    - [xen] AMD, IOMMU: Disable IOMMU if SATA Combined mode is on (Igor Mammedov) [910912 910913]     {CVE-2013-0153}
    - [xen] AMD, IOMMU: On creating entry clean up in remapping tables (Igor Mammedov) [910912 910913]     {CVE-2013-0153}
    - [xen] ACPI: acpi_table_parse() should return handler's err code (Igor Mammedov) [910912 910913]     {CVE-2013-0153}
    - [xen] introduce xzalloc() & Co (Igor Mammedov) [910912 910913] {CVE-2013-0153}

Tenable has extracted the preceding description block directly from the Oracle Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

From Red Hat Security Advisory 2013:0847 :

Updated kernel packages that fix one security issue and multiple bugs are now available for Red Hat Enterprise Linux 5.

The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

This update fixes the following security issue :

* A flaw was found in the way the Xen hypervisor AMD IOMMU driver handled interrupt remapping entries. By default, a single interrupt remapping table is used, and old interrupt remapping entries are not cleared, potentially allowing a privileged guest user in a guest that has a passed-through, bus-mastering capable PCI device to inject interrupt entries into others guests, including the privileged management domain (Dom0), leading to a denial of service.
(CVE-2013-0153, Moderate)

Red Hat would like to thank the Xen project for reporting the CVE-2013-0153 issue.

This update also fixes the following bugs :

* When a process is opening a file over NFSv4, sometimes an OPEN call can succeed while the following GETATTR operation fails with an NFS4ERR_DELAY error. The NFSv4 code did not handle such a situation correctly and allowed an NFSv4 client to attempt to use the buffer that should contain the GETATTR information. However, the buffer did not contain the valid GETATTR information, which caused the client to return a '-ENOTDIR' error. Consequently, the process failed to open the requested file. This update backports a patch that adds a test condition verifying validity of the GETATTR information. If the GETATTR information is invalid, it is obtained later and the process opens the requested file as expected. (BZ#947736)

* Previously, the xdr routines in NFS version 2 and 3 conditionally updated the res->count variable. Read retry attempts after a short NFS read() call could fail to update the res->count variable, resulting in truncated read data being returned. With this update, the res->count variable is updated unconditionally so this bug can no longer occur.
(BZ#952098)

* When handling requests from Intelligent Platform Management Interface (IPMI) clients, the IPMI driver previously used two different locks for an IPMI request. If two IPMI clients sent their requests at the same time, each request could receive one of the locks and then wait for the second lock to become available. This resulted in a deadlock situation and the system became unresponsive. The problem could occur more likely in environments with many IPMI clients. This update modifies the IPMI driver to handle the received messages using tasklets so the driver now uses a safe locking technique when handling IPMI requests and the mentioned deadlock can no longer occur. (BZ#953435)

* Incorrect locking around the cl_state_owners list could cause the NFSv4 state reclaimer thread to enter an infinite loop while holding the Big Kernel Lock (BLK). As a consequence, the NFSv4 client became unresponsive. With this update, safe list iteration is used, which prevents the NFSv4 client from hanging in this scenario. (BZ#954296)

Users should upgrade to these updated packages, which contain backported patches to correct these issues. The system must be rebooted for this update to take effect.

This update fixes the following security issue :

  - A flaw was found in the way the Xen hypervisor AMD IOMMU     driver handled interrupt remapping entries. By default,     a single interrupt remapping table is used, and old     interrupt remapping entries are not cleared, potentially     allowing a privileged guest user in a guest that has a     passed- through, bus-mastering capable PCI device to     inject interrupt entries into others guests, including     the privileged management domain (Dom0), leading to a     denial of service. (CVE-2013-0153, Moderate)

This update also fixes the following bugs :

  - When a process is opening a file over NFSv4, sometimes     an OPEN call can succeed while the following GETATTR     operation fails with an NFS4ERR_DELAY error. The NFSv4     code did not handle such a situation correctly and     allowed an NFSv4 client to attempt to use the buffer     that should contain the GETATTR information. However,     the buffer did not contain the valid GETATTR     information, which caused the client to return a     '-ENOTDIR' error. Consequently, the process failed to     open the requested file. This update backports a patch     that adds a test condition verifying validity of the     GETATTR information. If the GETATTR information is     invalid, it is obtained later and the process opens the     requested file as expected.

  - Previously, the xdr routines in NFS version 2 and 3     conditionally updated the res->count variable. Read     retry attempts after a short NFS read() call could fail     to update the res->count variable, resulting in     truncated read data being returned. With this update,     the res->count variable is updated unconditionally so     this bug can no longer occur.

  - When handling requests from Intelligent Platform     Management Interface (IPMI) clients, the IPMI driver     previously used two different locks for an IPMI request.
    If two IPMI clients sent their requests at the same     time, each request could receive one of the locks and     then wait for the second lock to become available. This     resulted in a deadlock situation and the system became     unresponsive. The problem could occur more likely in     environments with many IPMI clients. This update     modifies the IPMI driver to handle the received messages     using tasklets so the driver now uses a safe locking     technique when handling IPMI requests and the mentioned     deadlock can no longer occur.

  - Incorrect locking around the cl_state_owners list could     cause the NFSv4 state reclaimer thread to enter an     infinite loop while holding the Big Kernel Lock (BLK).
    As a consequence, the NFSv4 client became unresponsive.
    With this update, safe list iteration is used, which     prevents the NFSv4 client from hanging in this scenario.

The system must be rebooted for this update to take effect.

Updated kernel packages that fix one security issue and multiple bugs are now available for Red Hat Enterprise Linux 5.

The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

This update fixes the following security issue :

* A flaw was found in the way the Xen hypervisor AMD IOMMU driver handled interrupt remapping entries. By default, a single interrupt remapping table is used, and old interrupt remapping entries are not cleared, potentially allowing a privileged guest user in a guest that has a passed-through, bus-mastering capable PCI device to inject interrupt entries into others guests, including the privileged management domain (Dom0), leading to a denial of service.
(CVE-2013-0153, Moderate)

Red Hat would like to thank the Xen project for reporting the CVE-2013-0153 issue.

This update also fixes the following bugs :

* When a process is opening a file over NFSv4, sometimes an OPEN call can succeed while the following GETATTR operation fails with an NFS4ERR_DELAY error. The NFSv4 code did not handle such a situation correctly and allowed an NFSv4 client to attempt to use the buffer that should contain the GETATTR information. However, the buffer did not contain the valid GETATTR information, which caused the client to return a '-ENOTDIR' error. Consequently, the process failed to open the requested file. This update backports a patch that adds a test condition verifying validity of the GETATTR information. If the GETATTR information is invalid, it is obtained later and the process opens the requested file as expected. (BZ#947736)

* Previously, the xdr routines in NFS version 2 and 3 conditionally updated the res->count variable. Read retry attempts after a short NFS read() call could fail to update the res->count variable, resulting in truncated read data being returned. With this update, the res->count variable is updated unconditionally so this bug can no longer occur.
(BZ#952098)

* When handling requests from Intelligent Platform Management Interface (IPMI) clients, the IPMI driver previously used two different locks for an IPMI request. If two IPMI clients sent their requests at the same time, each request could receive one of the locks and then wait for the second lock to become available. This resulted in a deadlock situation and the system became unresponsive. The problem could occur more likely in environments with many IPMI clients. This update modifies the IPMI driver to handle the received messages using tasklets so the driver now uses a safe locking technique when handling IPMI requests and the mentioned deadlock can no longer occur. (BZ#953435)

* Incorrect locking around the cl_state_owners list could cause the NFSv4 state reclaimer thread to enter an infinite loop while holding the Big Kernel Lock (BLK). As a consequence, the NFSv4 client became unresponsive. With this update, safe list iteration is used, which prevents the NFSv4 client from hanging in this scenario. (BZ#954296)

Users should upgrade to these updated packages, which contain backported patches to correct these issues. The system must be rebooted for this update to take effect.

XEN has been updated to fix various bugs and security issues :

  - (XSA 36) To avoid an erratum in early hardware, the Xen     AMD IOMMU code by default choose to use a single     interrupt remapping table for the whole system. This     sharing implied that any guest with a passed through PCI     device that is bus mastering capable can inject     interrupts into other guests, including domain 0. This     has been disabled for AMD chipsets not capable of it.
    (CVE-2013-0153)

  - qemu: The e1000 had overflows under some conditions,     potentially corrupting memory. (CVE-2012-6075)

  - (XSA 37) Hypervisor crash due to incorrect ASSERT (debug     build only). (CVE-2013-0154)

  - (XSA-33) A VT-d interrupt remapping source validation     flaw was fixed. Also the following bugs have been fixed     :. (CVE-2012-5634)

  - xen hot plug attach/detach fails. (bnc#805094)

  - domain locking can prevent a live migration from     completing. (bnc#802690)

  - no way to control live migrations. (bnc#797014)

  - fix logic error in stdiostream_progress

  - restore logging in xc_save

  - add options to control migration tunables

  - enabling xentrace crashes hypervisor. (bnc#806736)

  - Upstream patches from Jan     26287-sched-credit-pick-idle.patch     26501-VMX-simplify-CR0-update.patch     26502-VMX-disable-SMEP-when-not-paging.patch     26516-ACPI-parse-table-retval.patch (Replaces     CVE-2013-0153-xsa36.patch)     26517-AMD-IOMMU-clear-irtes.patch (Replaces     CVE-2013-0153-xsa36.patch)     26518-AMD-IOMMU-disable-if-SATA-combined-mode.patch     (Replaces CVE-2013-0153-xsa36.patch)     26519-AMD-IOMMU-perdev-intremap-default.patch (Replaces     CVE-2013-0153-xsa36.patch) 26526-pvdrv-no-devinit.patch     26531-AMD-IOMMU-IVHD-special-missing.patch (Replaces     CVE-2013-0153-xsa36.patch)

  - Add $network to xend initscript dependencies.
    (bnc#798188)

  - Unable to dvd or cdrom-boot DomU after xen-tools update     Fixed with update to Xen version 4.1.4. (bnc#799694)

  - L3: HP iLo Generate NMI function not working in XEN     kernel. (bnc#800156)

  - Upstream patches from Jan     26404-x86-forward-both-NMI-kinds.patch     26427-x86-AMD-enable-WC+.patch

  - Xen VMs with more than 2 disks randomly fail to start.
    (bnc#793927)

  - Upstream patches from Jan     26332-x86-compat-show-guest-stack-mfn.patch     26333-x86-get_page_type-assert.patch (Replaces     CVE-2013-0154-xsa37.patch)     26340-VT-d-intremap-verify-legacy-bridge.patch (Replaces     CVE-2012-5634-xsa33.patch)     26370-libxc-x86-initial-mapping-fit.patch

  - Update to Xen 4.1.4 c/s 23432

  - Update xenpaging.guest-memusage.patch add rule for     xenmem to avoid spurious build failures

  - Upstream patches from Jan 26179-PCI-find-next-cap.patch     26183-x86-HPET-masking.patch     26188-x86-time-scale-asm.patch     26200-IOMMU-debug-verbose.patch     26203-x86-HAP-dirty-vram-leak.patch     26229-gnttab-version-switch.patch (Replaces     CVE-2012-5510-xsa26.patch)     26230-x86-HVM-limit-batches.patch (Replaces     CVE-2012-5511-xsa27.patch)     26231-memory-exchange-checks.patch (Replaces     CVE-2012-5513-xsa29.patch)     26232-x86-mark-PoD-error-path.patch (Replaces     CVE-2012-5514-xsa30.patch)     26233-memop-order-checks.patch (Replaces     CVE-2012-5515-xsa31.patch)     26235-IOMMU-ATS-max-queue-depth.patch     26272-x86-EFI-makefile-cflags-filter.patch     26294-x86-AMD-Fam15-way-access-filter.patch     CVE-2013-0154-xsa37.patch

  - Restore c/s 25751 in 23614-x86_64-EFI-boot.patch. Modify     the EFI Makefile to do additional filtering.

Multiple vulnerabilities have been discovered in the Xen hypervisor.
The Common Vulnerabilities and Exposures project identifies the following problems :

  - CVE-2012-4544     Insufficient validation of kernel or ramdisk sizes in     the Xen PV domain builder could result in denial of     service.

  - CVE-2012-5511     Several HVM control operations performed insufficient     validation of input, which could result in denial of     service through resource exhaustion.

  - CVE-2012-5634     Incorrect interrupt handling when using VT-d hardware     could result in denial of service.

  - CVE-2013-0153     Insufficient restriction of interrupt access could     result in denial of service.

adjust gcc 4.8 fixes guest using oxenstored can crash host or exhaust memory [XSA-38, CVE-2013-0215] (#907888), guest using AMD-Vi for PCI passthrough can cause denial of service [XSA-36, CVE-2013-0153] (#910914), fixes for gcc 4.8

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.

guest using oxenstored can crash host or exhaust memory [XSA-38, CVE-2013-0215] (#907888), guest using AMD-Vi for PCI passthrough can cause denial of service [XSA-36, CVE-2013-0153](#910914)

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
84140	OracleVM 3.2 : xen (OVMSA-2015-0068) (POODLE) (Venom)	Nessus	OracleVM Local Security Checks	low
83616	SUSE SLES11 Security Update : Xen (SUSE-SU-2014:0446-1)	Nessus	SuSE Local Security Checks	high
79500	OracleVM 3.2 : xen (OVMSA-2013-0011)	Nessus	OracleVM Local Security Checks	medium
79498	OracleVM 3.1 : xen (OVMSA-2013-0009)	Nessus	OracleVM Local Security Checks	medium
74967	openSUSE Security Update : xen (openSUSE-SU-2013:0637-1)	Nessus	SuSE Local Security Checks	high
74966	openSUSE Security Update : xen (openSUSE-SU-2013:0636-1)	Nessus	SuSE Local Security Checks	high
70184	GLSA-201309-24 : Xen: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	high
68826	Oracle Linux 5 : kernel (ELSA-2013-0847)	Nessus	Oracle Linux Local Security Checks	high
68825	Oracle Linux 5 : kernel (ELSA-2013-0847-1)	Nessus	Oracle Linux Local Security Checks	medium
66551	Scientific Linux Security Update : kernel on SL5.x i386/x86_64 (20130521)	Nessus	Scientific Linux Local Security Checks	medium
66536	RHEL 5 : kernel (RHSA-2013:0847)	Nessus	Red Hat Local Security Checks	medium
66528	CentOS 5 : kernel (CESA-2013:0847)	Nessus	CentOS Local Security Checks	medium
65797	SuSE 11.2 Security Update : Xen (SAT Patch Number 7492)	Nessus	SuSE Local Security Checks	high
64973	Debian DSA-2636-2 : xen - several vulnerabilities	Nessus	Debian Local Security Checks	medium
64678	Fedora 18 : xen-4.2.1-7.fc18 (2013-2225)	Nessus	Fedora Local Security Checks	medium
64650	Fedora 17 : xen-4.1.4-4.fc17 (2013-2002)	Nessus	Fedora Local Security Checks	medium

Detections

Analytics

CVE-2013-0153

high

Tenable Plugins

low

high

medium

medium

high

high

high

high

medium

medium

medium

medium

high

medium

medium

medium