update to xen-4.2.2 which includes security fixes, make xendomains work better with xl

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.

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

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]

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
66320	Fedora 18 : xen-4.2.2-1.fc18 (2013-6641)	Nessus	Fedora Local Security Checks	2013/5/5	2021/1/11	medium
66985	SuSE 11.2 Security Update : Xen (SAT Patch Number 7798)	Nessus	SuSE Local Security Checks	2013/6/26	2021/1/19	high
75130	openSUSE Security Update : xen (openSUSE-SU-2013:1404-1)	Nessus	SuSE Local Security Checks	2014/6/13	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

检测

插件搜索

medium

high

high

medium

medium

medium