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

  - CVE-2013-1918     ( XSA 45) several long latency operations are not     preemptible.

  Some page table manipulation operations for PV guests were not made   preemptible, allowing a malicious or buggy PV guest kernel to mount   a denial of service attack affecting the whole system.

  - CVE-2013-1952     ( XSA 49) VT-d interrupt remapping source validation     flaw for bridges.

  Due to missing source validation on interrupt remapping table   entries for MSI interrupts set up by bridge devices, a malicious   domain with access to such a device can mount a denial of service   attack affecting the whole system.

  - CVE-2013-1964     ( XSA 50) grant table hypercall acquire/release     imbalance.

  When releasing a particular, non-transitive grant after doing a   grant copy operation, Xen incorrectly releases an unrelated grant   reference, leading possibly to a crash of the host system.
  Furthermore information leakage or privilege escalation cannot be   ruled out.

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

  - VT-d: don't permit SVT_NO_VERIFY entries for known     device types Only in cases where we don't know what to     do we should leave the IRTE blank (suppressing all     validation), but we should always log a warning in those     cases (as being insecure). This is CVE-2013-1952 /     XSA-49.

  - x86: make page table handling error paths preemptible     ... as they may take significant amounts of time. This     requires cloning the tweaked continuation logic from     do_mmuext_op to do_mmu_update. Note that in     mod_l[34]_entry a negative 'preemptible' value gets     passed to put_page_from_l[34]e now, telling the callee     to store the respective page in     current->arch.old_guest_table (for a hypercall     continuation to pick up), rather than carrying out the     put right away. This is going to be made a little more     explicit by a subsequent cleanup patch. This is part of     CVE-2013-1918 / XSA-45. (CVE-2013-1918)

  - x86: make page table unpinning preemptible ... as it may     take significant amounts of time. Since we can't     re-invoke the operation in a second attempt, the     continuation logic must be slightly tweaked so that we     make sure do_mmuext_op gets run one more time even when     the preempted unpin operation was the last one in a     batch. This is part of CVE-2013-1918 / XSA-45.
    (CVE-2013-1918)

  - x86: make arch_set_info_guest preemptible .. as the root     page table validation (and the dropping of an eventual     old one) can require meaningful amounts of time. This is     part of CVE-2013-1918 / XSA-45. (CVE-2013-1918)

  - x86: make vcpu_reset preemptible ... as dropping the old     page tables may take significant amounts of time. This     is part of CVE-2013-1918 / XSA-45. (CVE-2013-1918)

  - x86: make MMUEXT_NEW_USER_BASEPTR preemptible ... as it     may take significant amounts of time. This is part of     CVE-2013-1918 / XSA-45. (CVE-2013-1918)

  - x86: make new_guest_cr3 preemptible ... as it may take     significant amounts of time. This is part of     CVE-2013-1918 / XSA-45. (CVE-2013-1918)

  - x86: make vcpu_destroy_pagetables preemptible ... as it     may take significant amounts of time. The function,     being moved to mm.c as the better home for it anyway,     and to avoid having to make a new helper function there     non-static, is given a 'preemptible' parameter     temporarily (until, in a subsequent patch, its other     caller is also being made capable of dealing with     preemption). This is part of CVE-2013-1918 / XSA-45.
    (CVE-2013-1918)

  - Fix rcu domain locking for transitive grants When     acquiring a transitive grant for copy then the owning     domain needs to be locked down as well as the granting     domain. This was being done, but the unlocking was not.
    The acquire code now stores the struct domain * of the     owning domain (rather than the domid) in the active     entry in the granting domain. The release code then does     the unlock on the owning domain. Note that I believe I     also fixed a bug where, for non-transitive grants the     active entry contained a reference to the acquiring     domain rather than the granting domain. From my reading     of the code this would stop the release code for     transitive grants from terminating its recursion     correctly.

    Also, for non-transitive grants we now avoid incorrectly     recursing in __release_grant_for_copy. This is     CVE-2013-1964 / XSA-50. (CVE-2013-1964)

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

- Thu Apr 25 2013 Michael Young <m.a.young at     durham.ac.uk> - 4.1.5-1

    - update to xen-4.1.5 includes fixes for passed through       IRQs or PCI devices might allow denial of service       attack [XSA-46, CVE-2013-1919] (#953568) SYSENTER in       32-bit PV guests on 64-bit xen can crash hypervisor       [XSA-44, CVE-2013-1917] (#953569) grant releases can       release more than intended potentially crashing xen       [XSA-50, CVE-2013-1964] (#953632)

  - remove patches that are included in 4.1.5

    - allow xendomains to work with xl saved images

    - Thu Apr 4 2013 Michael Young <m.a.young at       durham.ac.uk> - 4.1.4-7

    - make xendomains systemd script executable (#919705)

    - Potential use of freed memory in event channel       operations [XSA-47, CVE-2013-1920]

  - Fri Feb 22 2013 Michael Young <m.a.young at     durham.ac.uk> - 4.1.4-6

    - patch for [XSA-36, CVE-2013-0153] can cause boot time       crash

    - backport the fixes discovered when building with gcc       4.8

    - Fri Feb 15 2013 Michael Young <m.a.young at       durham.ac.uk> - 4.1.4-5

    - patch for [XSA-38, CVE-2013-0215] was flawed

    - Wed Feb 6 2013 Michael Young <m.a.young at       durham.ac.uk> - 4.1.4-4

    - 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)

  - Thu Jan 17 2013 Michael Young <m.a.young at     durham.ac.uk> - 4.1.4-3

    - Buffer overflow when processing large packets in qemu       e1000 device driver [XSA-41, CVE-2012-6075] (#910845)

  - fix a bug introduced by fix for XSA-27

    - Fri Jan 11 2013 Michael Young <m.a.young at       durham.ac.uk> - 4.1.4-2

    - VT-d interrupt remapping source validation flaw       [XSA-33, CVE-2012-5634] (#893568)

  - Tue Dec 18 2012 Michael Young <m.a.young at     durham.ac.uk> - 4.1.4-1

    - update to xen-4.1.4

    - remove patches that are included in 4.1.4

    - Tue Dec 4 2012 Michael Young <m.a.young at       durham.ac.uk> - 4.1.3-7

    - 6 security fixes A guest can cause xen to crash       [XSA-26, CVE-2012-5510] (#883082) An HVM guest can       cause xen to run slowly or crash [XSA-27,       CVE-2012-5511] (#883084) An HVM guest can cause xen to       crash or leak information [XSA-28, CVE-2012-5512]       (#883085) A PV guest can cause xen to crash and might       be able escalate privileges [XSA-29, CVE-2012-5513]       (#883088) An HVM guest can cause xen to hang [XSA-30,       CVE-2012-5514] (#883091) A guest can cause xen to hang       [XSA-31, CVE-2012-5515] (#883092)

  - Tue Nov 13 2012 Michael Young <m.a.young at     durham.ac.uk> - 4.1.3-6

    - 5 security fixes A guest can block a cpu by setting a       bad VCPU deadline [XSA 20, CVE-2012-4535] (#876198)

[plus 60 lines in the Changelog]

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.

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

  - VT-d: don't permit SVT_NO_VERIFY entries for known     device types Only in cases where we don't know what to     do we should leave the IRTE blank (suppressing all     validation), but we should always log a warning in those     cases (as being insecure). This is CVE-2013-1952 /     XSA-49. (CVE-2013-1952)

  - x86: make page table handling error paths preemptible     ... as they may take significant amounts of time. This     requires cloning the tweaked continuation logic from     do_mmuext_op to do_mmu_update. Note that in     mod_l[34]_entry a negative 'preemptible' value gets     passed to put_page_from_l[34]e now, telling the callee     to store the respective page in     current->arch.old_guest_table (for a hypercall     continuation to pick up), rather than carrying out the     put right away. This is going to be made a little more     explicit by a subsequent cleanup patch. This is part of     CVE-2013-1918 / XSA-45. (CVE-2013-1918)

  - x86: make page table unpinning preemptible ... as it may     take significant amounts of time. Since we can't     re-invoke the operation in a second attempt, the     continuation logic must be slightly tweaked so that we     make sure do_mmuext_op gets run one more time even when     the preempted unpin operation was the last one in a     batch. This is part of CVE-2013-1918 / XSA-45.
    (CVE-2013-1918) (CVE-2013-1918)

  - x86: make vcpu_reset preemptible ... as dropping the old     page tables may take significant amounts of time. This     is part of CVE-2013-1918 / XSA-45. (CVE-2013-1918)

  - x86: make MMUEXT_NEW_USER_BASEPTR preemptible ... as it     may take significant amounts of time. This is part of     CVE-2013-1918 / XSA-45. (CVE-2013-1918)

  - x86: make new_guest_cr3 preemptible ... as it may take     significant amounts of time. This is part of     CVE-2013-1918 / XSA-45. (CVE-2013-1918)

  - x86: make vcpu_destroy_pagetables preemptible ... as it     may take significant amounts of time. The function,     being moved to mm.c as the better home for it anyway,     and to avoid having to make a new helper function there     non-static, is given a 'preemptible' parameter     temporarily (until, in a subsequent patch, its other     caller is also being made capable of dealing with     preemption). This is part of CVE-2013-1918 / XSA-45.
    (CVE-2013-1918)

  - Fix rcu domain locking for transitive grants When     acquiring a transitive grant for copy then the owning     domain needs to be locked down as well as the granting     domain. This was being done, but the unlocking was not.
    The acquire code now stores the struct domain * of the     owning domain (rather than the domid) in the active     entry in the granting domain. The release code then does     the unlock on the owning domain. Note that I believe I     also fixed a bug where, for non-transitive grants the     active entry contained a reference to the acquiring     domain rather than the granting domain. From my reading     of the code this would stop the release code for     transitive grants from terminating its recursion     correctly.

    Also, for non-transitive grants we now avoid incorrectly     recursing in __release_grant_for_copy. This is     CVE-2013-1964 / XSA-50. (CVE-2013-1964)

XEN has been updated to 4.1.5 c/s 23509 to fix various bugs and security issues.

The following security issues have been fixed :

  - Certain page table manipulation operations in Xen 4.1.x,     4.2.x, and earlier were not preemptible, which allowed     local PV kernels to cause a denial of service via     vectors related to deep page table traversal.
    (CVE-2013-1918)

  - Xen 4.x, when using Intel VT-d for a bus mastering     capable PCI device, did not properly check the source     when accessing a bridge devices interrupt remapping     table entries for MSI interrupts, which allowed local     guest domains to cause a denial of service (interrupt     injection) via unspecified vectors. (CVE-2013-1952)

  - A information leak in the XSAVE/XRSTOR instructions     could be used to determine state of floating point     operations in other domains. (CVE-2013-2076)

  - A denial of service (hypervisor crash) was possible due     to missing exception recovery on XRSTOR, that could be     used to crash the machine by PV guest users.
    (CVE-2013-2077)

  - A denial of service (hypervisor crash) was possible due     to missing exception recovery on XSETBV, that could be     used to crash the machine by PV guest users.
    (CVE-2013-2078)

  - Systems which allow untrusted administrators to     configure guest vcpu affinity may be exploited to     trigger a buffer overrun and corrupt memory.
    (CVE-2013-2072)

  - Xen 3.1 through 4.x, when running 64-bit hosts on Intel     CPUs, did not clear the NT flag when using an IRET after     a SYSENTER instruction, which allowed 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. (CVE-2013-1917)

  - Xen 4.2.x and 4.1.x did not properly restrict access to     IRQs, which allowed 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.'.
    (CVE-2013-1919)

  - 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, used the wrong ordering of     operations when extending the per-domain event channel     tracking table, which caused a use-after-free and     allowed local guest kernels to inject arbitrary events     and gain privileges via unspecified vectors.
    (CVE-2013-1920)

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

Bugfixes :

  - Upstream patches from Jan     26956-x86-mm-preemptible-cleanup.patch     27071-x86-IO-APIC-fix-guest-RTE-write-corner-cases.patch     27072-x86-shadow-fix-off-by-one-in-MMIO-permission-check     .patch 27079-fix-XSA-46-regression-with-xend-xm.patch     27083-AMD-iommu-SR56x0-Erratum-64-Reset-all-head-tail-po     inters.patch

  - 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.

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

  - Upstream patches from Jan     26702-powernow-add-fixups-for-AMD-P-state-figures.patch     26704-x86-MCA-suppress-bank-clearing-for-certain-injecte     d-events.patch     26731-AMD-IOMMU-Process-softirqs-while-building-dom0-iom     mu-mappings.patch     26733-VT-d-Enumerate-IOMMUs-when-listing-capabilities.pa     tch     26734-ACPI-ERST-Name-table-in-otherwise-opaque-error-mes     sages.patch     26736-ACPI-APEI-Unlock-apei_iomaps_lock-on-error-path.pa     tch 26737-ACPI-APEI-Add-apei_exec_run_optional.patch     26742-IOMMU-properly-check-whether-interrupt-remapping-i     s-enabled.patch     26743-VT-d-deal-with-5500-5520-X58-errata.patch     26744-AMD-IOMMU-allow-disabling-only-interrupt-remapping     .patch     26749-x86-reserve-pages-when-SandyBridge-integrated-grap     hics.patch     26765-hvm-Clean-up-vlapic_reg_write-error-propagation.pa     tch     26770-x86-irq_move_cleanup_interrupt-must-ignore-legacy-     vectors.patch     26771-x86-S3-Restore-broken-vcpu-affinity-on-resume.patc     h     26772-VMX-Always-disable-SMEP-when-guest-is-in-non-pagin     g-mode.patch     26773-x86-mm-shadow-spurious-warning-when-unmapping-xenh     eap-pages.patch     26799-x86-don-t-pass-negative-time-to-gtime_to_gtsc.patc     h     26851-iommu-crash-Interrupt-remapping-is-also-disabled-o     n-crash.patch

  - Unable to create XEN virtual machines in SLED 11 SP2 on     Kyoto xend-cpuinfo-model-name.patch. (bnc#814709)

  - 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

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 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 : please see Oracle VM Security Advisory OVMSA-2015-0068 for details.

ID	Name	Product	Family	Published	Updated	Severity
66383	Debian DSA-2666-1 : xen - several vulnerabilities	Nessus	Debian Local Security Checks	5/13/2013	1/11/2021	medium
79506	OracleVM 3.1 : xen (OVMSA-2013-0037)	Nessus	OracleVM Local Security Checks	11/26/2014	1/4/2021	medium
70184	GLSA-201309-24 : Xen: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	9/28/2013	1/6/2021	high
66321	Fedora 17 : xen-4.1.5-1.fc17 (2013-6723)	Nessus	Fedora Local Security Checks	5/5/2013	1/11/2021	medium
79505	OracleVM 3.2 : xen (OVMSA-2013-0036)	Nessus	OracleVM Local Security Checks	11/26/2014	1/4/2021	medium
66985	SuSE 11.2 Security Update : Xen (SAT Patch Number 7798)	Nessus	SuSE Local Security Checks	6/26/2013	1/19/2021	high
75129	openSUSE Security Update : xen (openSUSE-SU-2013:1392-1)	Nessus	SuSE Local Security Checks	6/13/2014	1/19/2021	high
83616	SUSE SLES11 Security Update : Xen (SUSE-SU-2014:0446-1)	Nessus	SuSE Local Security Checks	5/20/2015	1/19/2021	high
84140	OracleVM 3.2 : xen (OVMSA-2015-0068) (POODLE) (Venom)	Nessus	OracleVM Local Security Checks	6/12/2015	1/4/2021	low

Detections

Analytics

Plugins Search

medium

medium

high

medium

medium

high

high

high

low