The remote OracleVM system is missing necessary patches to address critical security updates :

  - x86: check segment descriptor read result in 64-bit OUTS     emulation XSA-67 (Matthew Daley) [orabug 17571640]     (CVE-2013-4368)

  - x86: properly set up fbld emulation operand address     XSA-66 (Jan Beulich) [orabug 17472492] (CVE-2013-4361)

  - x86: properly handle hvm_copy_from_guest_[phys,virt]     errors XSA-63 (Jan Beulich) [orabug 17472461]     (CVE-2013-4355)

  - libxc: builder: limit maximum size of kernel/ramdisk     (Ian Campbell) [orabug 15852491] (CVE-2012-4544)

  - libxc: builder: Correct fix for CVE-2012-4544 (Ian     Campbell) [orabug 15852491] (CVE-2012-4544)

  - [PATCH 01/21] libelf: abolish libelf-relocate.c (Ian     Jackson) [orabug 16902308] (CVE-2013-2194 CVE-2013-2195     CVE-2013-2196)

  - [PATCH 02/21] libxc: introduce xc_dom_seg_to_ptr_pages     (Ian Jackson) [orabug 16902308] (CVE-2013-2194     CVE-2013-2195 CVE-2013-2196)

  - [PATCH 03/21] libxc: Fix range checking in     xc_dom_pfn_to_ptr etc. (Ian Jackson) [orabug 16902308]     (CVE-2013-2194 CVE-2013-2195 CVE-2013-2196)

  - [PATCH 04/21] libelf: abolish elf_sval and     elf_access_signed (Ian Jackson) [orabug 16902308]     (CVE-2013-2194 CVE-2013-2195 CVE-2013-2196)

  - [PATCH 05/21] libelf/xc_dom_load_elf_symtab: Do not use     'syms' uninitialised (Ian Jackson) [orabug 16902308]     (CVE-2013-2194 CVE-2013-2195 CVE-2013-2196)

  - [PATCH 06/21] libelf: introduce macros for memory access     and pointer handling (Ian Jackson) [orabug 16902308]     (CVE-2013-2194 CVE-2013-2195 CVE-2013-2196)

  - [PATCH 07/21] tools/xcutils/readnotes: adjust     print_l1_mfn_valid_note (Ian Jackson) [orabug 16902308]     (CVE-2013-2194 CVE-2013-2195 CVE-2013-2196)

  - [PATCH 08/21] libelf: check nul-terminated strings     properly (Ian Jackson) [orabug 16902308] (CVE-2013-2194     CVE-2013-2195 CVE-2013-2196)

  - [PATCH 09/21] libelf: check all pointer accesses (Ian     Jackson) [orabug 16902308] (CVE-2013-2194 CVE-2013-2195     CVE-2013-2196)

  - [PATCH 10/21] libelf: Check pointer references in     elf_is_elfbinary (Ian Jackson) [orabug 16902308]     (CVE-2013-2194 CVE-2013-2195 CVE-2013-2196)

  - [PATCH 11/21] libelf: Make all callers call     elf_check_broken (Ian Jackson) [orabug 16902308]     (CVE-2013-2194 CVE-2013-2195 CVE-2013-2196)

  - [PATCH 12/21] libelf: use C99 bool for booleans (Ian     Jackson) [orabug 16902308] (CVE-2013-2194 CVE-2013-2195     CVE-2013-2196)

  - [PATCH 13/21] libelf: use only unsigned integers (Ian     Jackson) [orabug 16902308] (CVE-2013-2194 CVE-2013-2195     CVE-2013-2196)

  - [PATCH 14/21] libxc: Introduce xc_bitops.h (Ian Jackson)     [orabug 16902308] (CVE-2013-2194 CVE-2013-2195     CVE-2013-2196)

  - [PATCH 15/21] libelf: check loops for running away (Ian     Jackson) [orabug 16902308] (CVE-2013-2194 CVE-2013-2195     CVE-2013-2196)

  - [PATCH 16/21] libelf: abolish obsolete macros (Ian     Jackson) [orabug 16902308] (CVE-2013-2194 CVE-2013-2195     CVE-2013-2196)

  - [PATCH 17/21] libxc: Add range checking to     xc_dom_binloader (Ian Jackson) [orabug 16902308]     (CVE-2013-2194 CVE-2013-2195 CVE-2013-2196)

  - [PATCH 18/21] libxc: check failure of xc_dom_*_to_ptr,     xc_map_foreign_range (Ian Jackson) [orabug 16902308]     (CVE-2013-2194 CVE-2013-2195 CVE-2013-2196)

  - [PATCH 19/21] libxc: check return values from malloc     (Ian Jackson) [orabug 16902308] (CVE-2013-2194     CVE-2013-2195 CVE-2013-2196)

  - [PATCH 20/21] libxc: range checks in xc_dom_p2m_host and
    _guest (Ian Jackson) [orabug 16902308] (CVE-2013-2194     CVE-2013-2195 CVE-2013-2196)

  - [PATCH 21/21] libxc: check blob size before proceeding     in xc_dom_check_gzip (Matthew Daley) [orabug 16902308]     (CVE-2013-2194 CVE-2013-2195 CVE-2013-2196)

  - libxc: define INVALID_MFN for the XSA-55 patchset (Chuck     Anderson) [orabug 16902308] (CVE-2013-2194 CVE-2013-2195     CVE-2013-2196)

  - fix page refcount handling in page table pin error path     (Andrew Cooper) [orabug 16949882] (CVE-2013-1432)

  - remove CVE-2013-1919 (Chuck Anderson) [orabug 16635741]     (CVE-2013-1919)

  - x86: make vcpu_destroy_pagetables preemptible (Jan     Beulich) [orabug 16714903] (CVE-2013-1918)

  - x86: make new_guest_cr3 preemptible (Jan Beulich)     [orabug 16714903] (CVE-2013-1918)

  - x86: make MMUEXT_NEW_USER_BASEPTR preemptible (Jan     Beulich) [orabug 16714903] (CVE-2013-1918)

  - x86: make vcpu_reset preemptible (Jan Beulich) [orabug     16714903] (CVE-2013-1918)

  - x86: make arch_set_info_guest preemptible (Jan Beulich)     [orabug 16714903] (CVE-2013-1918)

  - x86: make page table unpinning preemptible (Jan Beulich)     [orabug 16714903] (CVE-2013-1918)

  - x86: make page table handling error paths preemptible     (Jan Beulich) [orabug 16714903] (CVE-2013-1918)

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 :

  - defer event channel bucket pointer store until after XSM     checks Otherwise a dangling pointer can be left, which     would cause subsequent memory corruption as soon as the     space got re-allocated for some other purpose. This is     CVE-2013-1920 / XSA-47.

    John Haxby 

  - x86: fix various issues with handling guest IRQs

  - properly revoke IRQ access in map_domain_pirq error path

  - don't permit replacing an in use IRQ

  - don't accept inputs in the GSI range for     MAP_PIRQ_TYPE_MSI

  - track IRQ access permission in host IRQ terms, not guest     IRQ ones (and with that, also disallow Dom0 access to     IRQ0) This is CVE-2013-1919 / XSA-46.

  - x86: clear EFLAGS.NT in SYSENTER entry path ... as it     causes problems if we happen to exit back via IRET: In     the course of trying to handle the fault, the hypervisor     creates a stack frame by hand, and uses PUSHFQ to set     the respective EFLAGS field, but expects to be able to     IRET through that stack frame to the second portion of     the fixup code (which causes a #GP due to the stored     EFLAGS having NT set). And even if this worked (e.g if     we cleared NT in that path), it would then (through the     fail safe callback) cause a #GP in the guest with the     SYSENTER handler's first instruction as the source,     which in turn would allow guest user mode code to crash     the guest kernel. Inject a #GP on the fake (NULL)     address of the SYSENTER instruction instead, just like     in the case where the guest kernel didn't register a     corresponding entry point. On 32-bit we also need to     make sure we clear SYSENTER_CS for all CPUs (neither     #RESET nor #INIT guarantee this). This is CVE-2013-1917     / XSA-44. (CVE-2013-1917)

The remote OracleVM system is missing necessary patches to address critical security updates :

  - defer event channel bucket pointer store until after XSM     checks Otherwise a dangling pointer can be left, which     would cause subsequent memory corruption as soon as the     space got re-allocated for some other purpose. This is     CVE-2013-1920 / XSA-47.

  - x86: fix various issues with handling guest IRQs

  - properly revoke IRQ access in map_domain_pirq error path

  - don't permit replacing an in use IRQ

  - don't accept inputs in the GSI range for     MAP_PIRQ_TYPE_MSI

  - track IRQ access permission in host IRQ terms, not guest     IRQ ones (and with that, also disallow Dom0 access to     IRQ0) This is CVE-2013-1919 / XSA-46.

  - x86: clear EFLAGS.NT in SYSENTER entry path ... as it     causes problems if we happen to exit back via IRET: In     the course of trying to handle the fault, the hypervisor     creates a stack course of trying to handle the fault,     the hypervisor creates a stack frame by hand, and uses     PUSHFQ to set the respective EFLAGS field, but expects     to be able to IRET through that stack frame to the     second portion of the fixup code (which causes a #GP due     to the stored EFLAGS having NT set). And even if this     worked (e.g if we cleared NT in that path), it would     then (through the fail safe callback) cause a #GP in the     guest with the SYSENTER handler's first instruction as     the source, which in turn would allow guest user mode     code to crash the guest kernel. Inject a #GP on the fake     (NULL) address of the SYSENTER instruction instead, just     like in the case where the guest kernel didn't register     a corresponding entry point. On 32-bit we also need to     make sure we clear SYSENTER_CS for all CPUs (neither     #RESET nor #INIT guarantee this). This is CVE-2013-1917     / XSA-44. (CVE-2013-1917)

  - Current Xend allowing multiple call destroy for the same     domain, this lead multiple hard resets(FLR) for pci     pass-through, and some controller might failed. In our     test, we pass through 2 LSI HAB controllers to the PVHVM     guest, after guest brought up, call xm-destroy twice,     the adapters's BIOS will hung, and we had to reboot the     server to recovery it. BTW: I had send this patch to Xen     maillist, but developer said Xend will obsolete and     would not review and merge the fix.

The remote OracleVM system is missing necessary patches to address critical security updates :

  - fix error in first version of the XSA-44 patch (Chuck     Anderson) [orabug 16632878, 16694867] (CVE-2013-1917)

  - clear EFLAGS.NT in SYSENTER entry path (Andrew Cooper)     [orabug 16632878] (CVE-2013-1917)

  - fix various issues with handling guest IRQs (Jan     Beulich) [orabug 16635741] (CVE-2013-1919)

  - defer event channel bucket pointer store until after XSM     checks [orabug 16635980] (CVE-2013-1920)

  - tools: xend: tolerate empty state/*.xml (Konrad Wilk,     Joe Jin) [orabug 14683665]

XEN was updated to 4.2.2, fixing lots of bugs and several security issues.

Various upstream patches were also merged into this version by our developers.

Detailed buglist :

  - bnc#824676 - Failed to setup devices for vm instance     when start multiple vms simultaneously

  - bnc#817799 - sles9sp4 guest fails to start after     upgrading to sles11 sp3

  - bnc#826882 - xen: CVE-2013-1432: XSA-58: Page reference     counting error due to XSA-45/CVE-2013-1918 fixes

  - Add upstream patch to fix devid assignment in libxl     27184-libxl-devid-fix.patch

  - bnc#823608 - xen: XSA-57: libxl allows guest write     access to sensitive console related xenstore keys     27178-libxl-Restrict-permissions-on-PV-console-device-xe     nstore-nodes.patch

  - bnc#823011 - xen: XSA-55: Multiple vulnerabilities in     libelf PV kernel handling

  - bnc#808269 - Fully Virtualized Windows VM install is     failed on Ivy Bridge platforms with Xen kernel

  - bnc#801663 - performance of mirror lvm unsuitable for     production block-dmmd

  - bnc#817904 - [SLES11SP3 BCS Bug] Crashkernel fails to     boot after panic on XEN kernel SP3 Beta 4 and RC1

  - Upstream AMD Erratum patch from Jan

  - bnc#813675 - - xen: CVE-2013-1919: XSA-46: Several     access permission issues with IRQs for unprivileged     guests

  - bnc#820917 - CVE-2013-2076: xen: Information leak on     XSAVE/XRSTOR capable AMD CPUs (XSA-52)

  - bnc#820919 - CVE-2013-2077: xen: Hypervisor crash due to     missing exception recovery on XRSTOR (XSA-53)

  - bnc#820920 - CVE-2013-2078: xen: Hypervisor crash due to     missing exception recovery on XSETBV (XSA-54)

  - bnc#808085 - aacraid driver panics mapping INT A when     booting kernel-xen

  - bnc#817210 - openSUSE 12.3 Domain 0 doesn't boot with     i915 graphics controller under Xen with VT-d enabled

  - bnc#819416 - xen: CVE-2013-2072: XSA-56: Buffer overflow     in xencontrol Python bindings affecting xend

  - bnc#818183 - xen: CVE-2013-2007: XSA-51: qga set umask     0077 when daemonizing

  - add lndir to BuildRequires

  - remove     xen.migrate.tools_notify_restore_to_hangup_during_migrat     ion_--abort_if_busy.patch It changed migration protocol     and upstream wants a different solution

  - bnc#802221 - fix xenpaging readd     xenpaging.qemu.flush-cache.patch

  - bnc#808269 - Fully Virtualized Windows VM install is     failed on Ivy Bridge platforms with Xen kernel

  - Additional fix for bnc#816159     CVE-2013-1918-xsa45-followup.patch

  - bnc#817068 - Xen guest with >1 sr-iov vf won't start

  - Update to Xen 4.2.2 c/s 26064 The following recent     security patches are included in the tarball     CVE-2013-0151-xsa34.patch (bnc#797285)     CVE-2012-6075-xsa41.patch (bnc#797523)     CVE-2013-1917-xsa44.patch (bnc#813673)     CVE-2013-1919-xsa46.patch (bnc#813675)

  - bnc#816159 - xen: CVE-2013-1918: XSA-45: Several long     latency operations are not preemptible

  - bnc#816163 - xen: CVE-2013-1952: XSA-49: VT-d interrupt     remapping source validation flaw for bridges

  - bnc#809662 - can't use pv-grub to start domU (pygrub     does work) xen.spec

  - bnc#814709 - Unable to create XEN virtual machines in     SLED 11 SP2 on Kyoto

  - bnc#813673 - CVE-2013-1917: xen: Xen PV DoS     vulnerability with SYSENTER

  - bnc#813675 - CVE-2013-1919: xen: Several access     permission issues with IRQs for unprivileged guests

  - bnc#814059 - xen: qemu-nbd format-guessing due to     missing format specification

XEN was updated to 4.1.5 release. It fixes various bugs and security issues.

Issues fixed separately from the 4.1.5 release :

  - bnc#824676 - Failed to setup devices for vm instance     when start multiple vms simultaneously 

  - bnc#XXXXXX - xen: CVE-2013-XXXX: XSA-61: suppress device     assignment to HVM guest when there is no IOMMU

  - Various upstream patches from Jan were integrated.

  - bnc#823786 - migrate.py support of short options dropped     by PTF

  - bnc#803712 - after live migration rcu_sched_state     detected stalls add new option xm migrate --min_remaing     <num>

  - CVE-2013-1432 / bnc#826882 - xen: XSA-58: x86: fix page     refcount handling in page table pin error path

  - CVE-2013-2211 / bnc#823608 - xen: XSA-57: libxl allows     guest write access to sensitive console related xenstore     keys

  - bnc#823011 - xen: XSA-55: Multiple vulnerabilities in     libelf PV kernel handling

  - bnc#801663 - performance of mirror lvm unsuitable for     production

  - CVE-2013-1918/ bnc#816159 - xen: CVE-2013-1918: XSA-45:
    Several long latency operations are not preemptible

  - CVE-2013-1952 / bnc#816163 - xen: CVE-2013-1952: XSA-49:
    VT-d interrupt remapping source validation flaw for     bridges

  - CVE-2013-2076 / bnc#820917 - CVE-2013-2076: xen:
    Information leak on XSAVE/XRSTOR capable AMD CPUs     (XSA-52)

  - CVE-2013-2077 / bnc#820919 - CVE-2013-2077: xen:
    Hypervisor crash due to missing exception recovery on     XRSTOR (XSA-53)

  - CVE-2013-2078 / bnc#820920 - CVE-2013-2078: xen:
    Hypervisor crash due to missing exception recovery on     XSETBV (XSA-54)

  - CVE-2013-2072 / bnc#819416 - xen: CVE-2013-2072: XSA-56:
    Buffer overflow in xencontrol Python bindings affecting     xend 

  - Update to Xen 4.1.5 c/s 23509 There were many xen.spec     file patches dropped as now being included in the 4.1.5     tarball.

  - CVE-2013-1918 / bnc#816159 - xen: XSA-45: Several long     latency operations are not preemptible

  - CVE-2013-1952 / bnc#816163 - xen: XSA-49: VT-d interrupt     remapping source validation flaw for bridges

  - bnc#809662 - can't use pv-grub to start domU (pygrub     does work)

  - CVE-2013-1917 / bnc#813673 - xen: Xen PV DoS     vulnerability with SYSENTER

  - CVE-2013-1919 / bnc#813675 - xen: Several access     permission issues with IRQs for unprivileged guests

  - CVE-2013-1920 / bnc#813677 - xen: Potential use of freed     memory in event channel operations

  - bnc#814709 - Unable to create XEN virtual machines in     SLED 11 SP2 on Kyoto

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

ID	名前	製品	ファミリー	公開日	更新日	深刻度
79521	OracleVM 2.2 : xen (OVMSA-2013-0074)	Nessus	OracleVM Local Security Checks	2014/11/26	2021/1/4	high
83616	SUSE SLES11 Security Update : Xen (SUSE-SU-2014:0446-1)	Nessus	SuSE Local Security Checks	2015/5/20	2021/1/19	high
79502	OracleVM 3.2 : xen (OVMSA-2013-0031)	Nessus	OracleVM Local Security Checks	2014/11/26	2021/1/4	medium
79503	OracleVM 3.1 : xen (OVMSA-2013-0032)	Nessus	OracleVM Local Security Checks	2014/11/26	2021/1/4	medium
79504	OracleVM 2.2 : xen (OVMSA-2013-0033)	Nessus	OracleVM Local Security Checks	2014/11/26	2021/1/4	medium
75130	openSUSE Security Update : xen (openSUSE-SU-2013:1404-1)	Nessus	SuSE Local Security Checks	2014/6/13	2021/1/19	high
75129	openSUSE Security Update : xen (openSUSE-SU-2013:1392-1)	Nessus	SuSE Local Security Checks	2014/6/13	2021/1/19	high
84140	OracleVM 3.2 : xen (OVMSA-2015-0068) (POODLE) (Venom)	Nessus	OracleVM Local Security Checks	2015/6/12	2021/1/4	low

検出

プラグインの検索

high

high

medium

medium

medium

high

high

low