The Linux kernel before 2.6.16.9 and the FreeBSD kernel, when running on AMD64 and other 7th and 8th generation AuthenticAMD processors, only save/restore the FOP, FIP, and FDP x87 registers in FXSAVE/FXRSTOR when an exception is pending, which allows one process to determine portions of the state of floating point instructions of other processes, which can be leveraged to obtain sensitive information such as cryptographic keys. 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.

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 :

  - x86/xsave: properly check guest input to XSETBV Other     than the HVM emulation path, the PV case so far failed     to check that YMM state requires SSE state to be     enabled, allowing for a #GP to occur upon passing the     inputs to XSETBV inside the hypervisor. This is     CVE-2013-2078 / XSA-54. (CVE-2013-2078)

  - 86/xsave: recover from faults on XRSTOR Just like     FXRSTOR, XRSTOR can raise #GP if bad content is being     passed to it in the memory block (i.e. aspects not under     the control of the hypervisor, other than e.g. proper     alignment of the block). Also correct the comment     explaining why FXRSTOR needs exception recovery code to     not wrongly state that this can only be a result of the     control tools passing a bad image. This is CVE-2013-2077     / XSA-53. (CVE-2013-2077)

  - x86/xsave: fix information leak on AMD CPUs Just like     for FXSAVE/FXRSTOR, XSAVE/XRSTOR also don't save/restore     the last instruction and operand pointers as well as the     last opcode if there's no pending unmasked exception     (see CVE-2006-1056 and commit 9747:4d667a139318). While     the FXSR solution sits in the save path, I prefer to     have this in the restore path because there the handling     is simpler (namely in the context of the pending changes     to properly save the selector values for 32-bit guest     code). Also this is using FFREE instead of EMMS, as it     doesn't seem unlikely that in the future we may see CPUs     with x87 and SSE/AVX but no MMX support. The goal here     anyway is just to avoid an FPU stack overflow. I would     have preferred to use FFREEP instead of FFREE (freeing     two stack slots at once), but AMD doesn't document that     instruction. This is CVE-2013-2076 / XSA-52.
    (CVE-2013-2076)

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

  - Other than the HVM emulation path, the PV case so far     failed to check that YMM state requires SSE state to be     enabled, allowing for a #GP to occur upon passing the     inputs to XSETBV inside the hypervisor. This is     CVE-2013-2078 / XSA-54. (CVE-2013-2078)

  - x86/xsave: recover from faults on XRSTOR Just like     FXRSTOR, XRSTOR can raise #GP if bad content is being     passed to it in the memory block (i.e. aspects not under     the control of the hypervisor, other than e.g. proper     alignment of the block). Also correct the comment     explaining why FXRSTOR needs exception recovery code to     not wrongly state that this can only be a result of the     control tools passing a bad image. This is CVE-2013-2077     / XSA-53. (CVE-2013-2077)

  - x86/xsave: fix information leak on AMD CPUs Just like     for FXSAVE/FXRSTOR, XSAVE/XRSTOR also don't save/restore     the last instruction and operand pointers as well as the     last opcode if there's no pending unmasked exception     (see CVE-2006-1056 and commit 9747:4d667a139318). While     the FXSR solution sits in the save path, I prefer to     have this in the restore path because there the handling     is simpler (namely in the context of the pending changes     to properly save the selector values for 32-bit guest     code). Also this is using FFREE instead of EMMS, as it     doesn't seem unlikely that in the future we may see CPUs     with x87 and SSE/AVX but no MMX support. The goal here     anyway is just to avoid an FPU stack overflow. I would     have preferred to use FFREEP instead of FFREE (freeing     two stack slots at once), but AMD doesn't document that     instruction. This is CVE-2013-2076 / XSA-52.
    (CVE-2013-2076)

An integer overflow was discovered in the do_replace() function. A local user process with the CAP_NET_ADMIN capability could exploit this to execute arbitrary commands with full root privileges. However, none of Ubuntu's supported packages use this capability with any non-root user, so this only affects you if you use some third party software like the OpenVZ virtualization system. (CVE-2006-0038)

On EMT64 CPUs, the kernel did not properly handle uncanonical return addresses. A local user could exploit this to trigger a kernel crash.
(CVE-2006-0744)

Al Viro discovered a local Denial of Service in the sysfs write buffer handling. By writing a block with a length exactly equal to the processor's page size to any writable file in /sys, a local attacker could cause a kernel crash. (CVE-2006-1055)

Jan Beulich discovered an information leak in the handling of registers for the numeric coprocessor when running on AMD processors.
This allowed processes to see the coprocessor execution state of other processes, which could reveal sensitive data in the case of cryptographic computations. (CVE-2006-1056)

Marcel Holtmann discovered that the sys_add_key() did not check that a new user key is added to a proper keyring. By attempting to add a key to a normal user key (which is not a keyring), a local attacker could exploit this to crash the kernel. (CVE-2006-1522)

Ingo Molnar discovered that the SCTP protocol connection tracking module in netfilter got stuck in an infinite loop on certain empty packet chunks. A remote attacker could exploit this to cause the computer to hang. (CVE-2006-1527)

The SCSI I/O driver did not correctly handle the VM_IO flag for memory mapped pages used for data transfer. A local user could exploit this to cause a kernel crash. (CVE-2006-1528)

The choose_new_parent() contained obsolete debugging code. A local user could exploit this to cause a kernel crash. (CVE-2006-1855)

Kostik Belousov discovered that the readv() and writev() functions did not query LSM modules for access permission. This could be exploited to circumvent access restrictions defined by LSM modules such as SELinux or AppArmor. (CVE-2006-1856)

The SCTP driver did not properly verify certain parameters when receiving a HB-ACK chunk. By sending a specially crafted packet to an SCTP socket, a remote attacker could exploit this to trigger a buffer overflow, which could lead to a crash or possibly even arbitrary code execution. (CVE-2006-1857)

The sctp_walk_params() function in the SCTP driver incorrectly used rounded values for bounds checking instead of the precise values. By sending a specially crafted packet to an SCTP socket, a remote attacker could exploit this to crash the kernel. (CVE-2006-1858)

Bjoern Steinbrink reported a memory leak in the __setlease() function.
A local attacker could exploit this to exhaust kernel memory and render the computer unusable (Denial of Service). (CVE-2006-1859)

Daniel Hokka Zakrisson discovered that the lease_init() did not properly handle locking. A local attacker could exploit this to cause a kernel deadlock (Denial of Service). (CVE-2006-1860)

Mark Moseley discovered that the CIFS file system driver did not filter out '..\\' path components. A local attacker could exploit this to break out of a chroot environment on a mounted SMB share.
(CVE-2006-1863) The same vulnerability applies to the older smb file system. (CVE-2006-1864)

Hugh Dickins discovered that the mprotect() function allowed an user to change a read-only shared memory attachment to become writable, which bypasses IPC (inter-process communication) permissions.
(CVE-2006-2071)

The SCTP (Stream Control Transmission Protocol) driver triggered a kernel panic on unexpected packets while the session was in the CLOSED state, instead of silently ignoring the packets. A remote attacker could exploit this to crash the computer. (CVE-2006-2271)

The SCTP driver did not handle control chunks if they arrived in fragmented packets. By sending specially crafted packets to an SCTP socket, a remote attacker could exploit this to crash the target machine. (CVE-2006-2272)

The SCTP driver did not correctly handle packets containing more than one DATA fragment. By sending specially crafted packets to an SCTP socket, a remote attacker could exploit this to crash the target machine. (CVE-2006-2274)

The SCTP driver did not correcly buffer incoming packets. By sending a large number of small messages to a receiver application that cannot process the messages quickly enough, a remote attacker could exploit this to cause a deadlock in the target machine (Denial of Service).
(CVE-2006-2275)

Patrick McHardy discovered that the snmp_trap_decode() function did not correctly handle memory allocation in some error conditions. By sending specially crafted packets to a machine which uses the SNMP network address translation (NAT), a remote attacker could exploit this to crash that machine. (CVE-2006-2444)

In addition, the Ubuntu 6.06 LTS update fixes a range of bugs.

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

Several local and remote vulnerabilities have been discovered in the Linux kernel that may lead to a denial of service or the execution of arbitrary code. The Common Vulnerabilities and Exposures project identifies the following problems :

  - CVE-2005-3359     Franz Filz discovered that some socket calls permit     causing inconsistent reference counts on loadable     modules, which allows local users to cause a denial of     service.

  - CVE-2006-0038     'Solar Designer' discovered that arithmetic computations     in netfilter's do_replace() function can lead to a     buffer overflow and the execution of arbitrary code.
    However, the operation requires CAP_NET_ADMIN     privileges, which is only an issue in virtualization     systems or fine grained access control systems.

  - CVE-2006-0039     'Solar Designer' discovered a race condition in     netfilter's do_add_counters() function, which allows     information disclosure of kernel memory by exploiting a     race condition. Likewise, it requires CAP_NET_ADMIN     privileges. 

  - CVE-2006-0456     David Howells discovered that the s390 assembly version     of the strnlen_user() function incorrectly returns some     string size values.

  - CVE-2006-0554     It was discovered that the ftruncate() function of XFS     can expose unallocated blocks, which allows information     disclosure of previously deleted files.

  - CVE-2006-0555     It was discovered that some NFS file operations on     handles mounted with O_DIRECT can force the kernel into     a crash.

  - CVE-2006-0557     It was discovered that the code to configure memory     policies allows tricking the kernel into a crash, thus     allowing denial of service.

  - CVE-2006-0558     It was discovered by Cliff Wickman that perfmon for the     IA64 architecture allows users to trigger a BUG()     assert, which allows denial of service.

  - CVE-2006-0741     Intel EM64T systems were discovered to be susceptible to     a local DoS due to an endless recursive fault related to     a bad ELF entry address.

  - CVE-2006-0742     Alan and Gareth discovered that the ia64 platform had an     incorrectly declared die_if_kernel() function as 'does     never return' which could be exploited by a local     attacker resulting in a kernel crash.

  - CVE-2006-0744     The Linux kernel did not properly handle uncanonical     return addresses on Intel EM64T CPUs, reporting     exceptions in the SYSRET instead of the next     instruction, causing the kernel exception handler to run     on the user stack with the wrong GS. This may result in     a DoS due to a local user changing the frames.

  - CVE-2006-1056     AMD64 machines (and other 7th and 8th generation     AuthenticAMD processors) were found to be vulnerable to     sensitive information leakage, due to how they handle     saving and restoring the FOP, FIP, and FDP x87 registers     in FXSAVE/FXRSTOR when an exception is pending. This     allows a process to determine portions of the state of     floating point instructions of other processes.

  - CVE-2006-1242     Marco Ivaldi discovered that there was an unintended     information disclosure allowing remote attackers to     bypass protections against Idle Scans (nmap -sI) by     abusing the ID field of IP packets and bypassing the     zero IP ID in DF packet countermeasure. This was a     result of the ip_push_pending_frames function improperly     incremented the IP ID field when sending a RST after     receiving unsolicited TCP SYN-ACK packets.

  - CVE-2006-1368     Shaun Tancheff discovered a buffer overflow (boundary     condition error) in the USB Gadget RNDIS implementation     allowing remote attackers to cause a DoS. While creating     a reply message, the driver allocated memory for the     reply data, but not for the reply structure. The kernel     fails to properly bounds-check user-supplied data before     copying it to an insufficiently sized memory buffer.
    Attackers could crash the system, or possibly execute     arbitrary machine code.

  - CVE-2006-1523     Oleg Nesterov reported an unsafe BUG_ON call in signal.c     which was introduced by RCU signal handling. The BUG_ON     code is protected by siglock while the code in     switch_exit_pids() uses tasklist_lock. It may be     possible for local users to exploit this to initiate a     denial of service attack (DoS).

  - CVE-2006-1524     Hugh Dickins discovered an issue in the madvise_remove()     function wherein file and mmap restrictions are not     followed, allowing local users to bypass IPC permissions     and replace portions of readonly tmpfs files with     zeroes.

  - CVE-2006-1525     Alexandra Kossovsky reported a NULL pointer dereference     condition in ip_route_input() that can be triggered by a     local user by requesting a route for a multicast IP     address, resulting in a denial of service (panic).

  - CVE-2006-1857     Vlad Yasevich reported a data validation issue in the     SCTP subsystem that may allow a remote user to overflow     a buffer using a badly formatted HB-ACK chunk, resulting     in a denial of service.

  - CVE-2006-1858     Vlad Yasevich reported a bug in the bounds checking code     in the SCTP subsystem that may allow a remote attacker     to trigger a denial of service attack when rounded     parameter lengths are used to calculate parameter     lengths instead of the actual values.

  - CVE-2006-1863     Mark Mosely discovered that chroots residing on an CIFS     share can be escaped with specially crafted 'cd'     sequences.

  - CVE-2006-1864     Mark Mosely discovered that chroots residing on an SMB     share can be escaped with specially crafted 'cd'     sequences.

  - CVE-2006-2271     The 'Mu security team' discovered that carefully crafted     ECNE chunks can cause a kernel crash by accessing     incorrect state stable entries in the SCTP networking     subsystem, which allows denial of service.

  - CVE-2006-2272     The 'Mu security team' discovered that fragmented SCTP     control chunks can trigger kernel panics, which allows     for denial of service attacks.

  - CVE-2006-2274     It was discovered that SCTP packets with two initial     bundled data packets can lead to infinite recursion,     which allows for denial of service attacks.

Several local and remote vulnerabilities have been discovered in the Linux kernel that may lead to a denial of service or the execution of arbitrary code. The Common Vulnerabilities and Exposures project identifies the following problems :

  - CVE-2006-0038     'Solar Designer' discovered that arithmetic computations     in netfilter's do_replace() function can lead to a     buffer overflow and the execution of arbitrary code.
    However, the operation requires CAP_NET_ADMIN     privileges, which is only an issue in virtualization     systems or fine grained access control systems.

  - CVE-2006-0039     'Solar Designer' discovered a race condition in     netfilter's do_add_counters() function, which allows     information disclosure of kernel memory by exploiting a     race condition. Like CVE-2006-0038, it requires     CAP_NET_ADMIN privileges.

  - CVE-2006-0741     Intel EM64T systems were discovered to be susceptible to     a local DoS due to an endless recursive fault related to     a bad ELF entry address.

  - CVE-2006-0742     Incorrectly declared die_if_kernel() function as 'does     never return' which could be exploited by a local     attacker resulting in a kernel crash.

  - CVE-2006-1056     AMD64 machines (and other 7th and 8th generation     AuthenticAMD processors) were found to be vulnerable to     sensitive information leakage, due to how they handle     saving and restoring the FOP, FIP, and FDP x87 registers     in FXSAVE/FXRSTOR when an exception is pending. This     allows a process to determine portions of the state of     floating point instructions of other processes.

  - CVE-2006-1242     Marco Ivaldi discovered that there was an unintended     information disclosure allowing remote attackers to     bypass protections against Idle Scans (nmap -sI) by     abusing the ID field of IP packets and bypassing the     zero IP ID in DF packet countermeasure. This was a     result of the ip_push_pending_frames function improperly     incremented the IP ID field when sending a RST after     receiving unsolicited TCP SYN-ACK packets.

  - CVE-2006-1343     Pavel Kankovsky reported the existence of a potential     information leak resulting from the failure to     initialize sin.sin_zero in the IPv4 socket code.

  - CVE-2006-1368     Shaun Tancheff discovered a buffer overflow (boundary     condition error) in the USB Gadget RNDIS implementation     allowing remote attackers to cause a DoS. While creating     a reply message, the driver allocated memory for the     reply data, but not for the reply structure. The kernel     fails to properly bounds-check user-supplied data before     copying it to an insufficiently sized memory buffer.
    Attackers could crash the system, or possibly execute     arbitrary machine code.

  - CVE-2006-1524     Hugh Dickins discovered an issue in the madvise_remove()     function wherein file and mmap restrictions are not     followed, allowing local users to bypass IPC permissions     and replace portions of readonly tmpfs files with     zeroes.

  - CVE-2006-1525     Alexandra Kossovsky reported a NULL pointer dereference     condition in ip_route_input() that can be triggered by a     local user by requesting a route for a multicast IP     address, resulting in a denial of service (panic).

  - CVE-2006-1857     Vlad Yasevich reported a data validation issue in the     SCTP subsystem that may allow a remote user to overflow     a buffer using a badly formatted HB-ACK chunk, resulting     in a denial of service.

  - CVE-2006-1858     Vlad Yasevich reported a bug in the bounds checking code     in the SCTP subsystem that may allow a remote attacker     to trigger a denial of service attack when rounded     parameter lengths are used to calculate parameter     lengths instead of the actual values.

  - CVE-2006-1864     Mark Mosely discovered that chroots residing on an SMB     share can be escaped with specially crafted 'cd'     sequences.

  - CVE-2006-2271     The 'Mu security team' discovered that carefully crafted     ECNE chunks can cause a kernel crash by accessing     incorrect state stable entries in the SCTP networking     subsystem, which allows denial of service.

  - CVE-2006-2272     The 'Mu security team' discovered that fragmented SCTP     control chunks can trigger kernel panics, which allows     for denial of service attacks.

  - CVE-2006-2274     It was discovered that SCTP packets with two initial     bundled data packets can lead to infinite recursion,     which allows for denial of service attacks.

Updated kernel packages are now available as part of ongoing support and maintenance of Red Hat Enterprise Linux version 4.

This update has been rated as having important security impact by the Red Hat Security Response Team.

The Linux kernel handles the basic functions of the operating system.

This is the fourth regular update to Red Hat Enterprise Linux 4.

New features introduced in this update include :

* Device Mapper mirroring support

* IDE diskdump support

* x86, AMD64 and Intel EM64T: Multi-core scheduler support enhancements

* Itanium: perfmon support for Montecito

* much improved support for IBM x460

* AMD PowerNow! patches to support Opteron Rev G

* Vmalloc support > 64MB

The following device drivers have been upgraded to new versions :

ipmi: 33.11 to 33.13 ib_mthca: 0.06 to 0.08 bnx2: 1.4.30 to 1.4.38 bonding: 2.6.1 to 2.6.3 e100: 3.4.8-k2-NAPI to 3.5.10-k2-NAPI e1000:
6.1.16-k3-NAPI to 7.0.33-k2-NAPI sky2: 0.13 to 1.1 tg3: 3.43-rh to 3.52-rh ipw2100: 1.1.0 to git-1.1.4 ipw2200: 1.0.0 to git-1.0.10 3w-9xxx: 2.26.02.001 to 2.26.04.010 ips: 7.10.18 to 7.12.02 iscsi_sfnet: 4:0.1.11-2 to 4:0.1.11-3 lpfc: 0:8.0.16.18 to 0:8.0.16.27 megaraid_sas: 00.00.02.00 to 00.00.02.03-RH1 qla2xxx: 8.01.02-d4 to 8.01.04-d7 qla6312: 8.01.02-d4 to 8.01.04-d7 sata_promise: 1.03 to 1.04 sata_vsc: 1.1 to 1.2 ibmvscsic: 1.5.5 to 1.5.6 ipr: 2.0.11.1 to 2.0.11.2

Added drivers :

dcdbas: 5.6.0-2 sata_mv: 0.6 sata_qstor: 0.05 sata_uli: 0.5 skge: 1.1 stex: 2.9.0.13 pdc_adma: 0.03

This update includes fixes for the security issues :

* a flaw in the USB devio handling of device removal that allowed a local user to cause a denial of service (crash) (CVE-2005-3055, moderate)

* a flaw in the ACL handling of nfsd that allowed a remote user to bypass ACLs for readonly mounted NFS file systems (CVE-2005-3623, moderate)

* a flaw in the netfilter handling that allowed a local user with CAP_NET_ADMIN rights to cause a buffer overflow (CVE-2006-0038, low)

* a flaw in the IBM S/390 and IBM zSeries strnlen_user() function that allowed a local user to cause a denial of service (crash) or to retrieve random kernel data (CVE-2006-0456, important)

* a flaw in the keyctl functions that allowed a local user to cause a denial of service (crash) or to read sensitive kernel memory (CVE-2006-0457, important)

* a flaw in unaligned accesses handling on Itanium processors that allowed a local user to cause a denial of service (crash) (CVE-2006-0742, important)

* a flaw in SELinux ptrace logic that allowed a local user with ptrace permissions to change the tracer SID to a SID of another process (CVE-2006-1052, moderate)

* an info leak on AMD-based x86 and x86_64 systems that allowed a local user to retrieve the floating point exception state of a process run by a different user (CVE-2006-1056, important)

* a flaw in IPv4 packet output handling that allowed a remote user to bypass the zero IP ID countermeasure on systems with a disabled firewall (CVE-2006-1242, low)

* a minor info leak in socket option handling in the network code (CVE-2006-1343, low)

* a flaw in the HB-ACK chunk handling of SCTP that allowed a remote user to cause a denial of service (crash) (CVE-2006-1857, moderate)

* a flaw in the SCTP implementation that allowed a remote user to cause a denial of service (deadlock) (CVE-2006-2275, moderate)

* a flaw in the socket buffer handling that allowed a remote user to cause a denial of service (panic) (CVE-2006-2446, important)

* a flaw in the signal handling access checking on PowerPC that allowed a local user to cause a denial of service (crash) or read arbitrary kernel memory on 64-bit systems (CVE-2006-2448, important)

* a flaw in the netfilter SCTP module when receiving a chunkless packet that allowed a remote user to cause a denial of service (crash) (CVE-2006-2934, important)

There were several bug fixes in various parts of the kernel. The ongoing effort to resolve these problems has resulted in a marked improvement in the reliability and scalability of Red Hat Enterprise Linux 4.

Updated kernel packages are now available as part of ongoing support and maintenance of Red Hat Enterprise Linux version 3. This is the eighth regular update.

This security advisory has been rated as having important security impact by the Red Hat Security Response Team.

The Linux kernel handles the basic functions of the operating system.

This is the eighth regular kernel update to Red Hat Enterprise Linux 3.

New features introduced by this update include :

  - addition of the adp94xx and dcdbas device drivers -     diskdump support on megaraid_sas, qlogic, and swap     partitions - support for new hardware via driver and     SCSI white-list updates

There were many bug fixes in various parts of the kernel. The ongoing effort to resolve these problems has resulted in a marked improvement in the reliability and scalability of Red Hat Enterprise Linux 3.

There were numerous driver updates and security fixes (elaborated below). Other key areas affected by fixes in this update include the networking subsystem, the NFS and autofs4 file systems, the SCSI and USB subsystems, and architecture-specific handling affecting AMD Opteron and Intel EM64T processors.

The following device drivers have been added or upgraded to new versions :

adp94xx -------- 1.0.8 (new) bnx2 ----------- 1.4.38 cciss ---------- 2.4.60.RH1 dcdbas --------- 5.6.0-1 (new) e1000 ---------- 7.0.33-k2 emulex --------- 7.3.6 forcedeth ------ 0.30 ipmi ----------- 35.13 qlogic --------- 7.07.04b6 tg3 ------------ 3.52RH

The following security bugs were fixed in this update :

  - a flaw in the USB devio handling of device removal that     allowed a local user to cause a denial of service     (crash) (CVE-2005-3055, moderate)

  - a flaw in the exec() handling of multi-threaded tasks     using ptrace() that allowed a local user to cause a     denial of service (hang of a user process)     (CVE-2005-3107, low)

  - a difference in 'sysretq' operation of EM64T (as opposed     to Opteron) processors that allowed a local user to     cause a denial of service (crash) upon return from     certain system calls (CVE-2006-0741 and CVE-2006-0744,     important)

  - a flaw in unaligned accesses handling on Intel Itanium     processors that allowed a local user to cause a denial     of service (crash) (CVE-2006-0742, important)

  - an info leak on AMD-based x86 and x86_64 systems that     allowed a local user to retrieve the floating point     exception state of a process run by a different user     (CVE-2006-1056, important)

  - a flaw in IPv4 packet output handling that allowed a     remote user to bypass the zero IP ID countermeasure on     systems with a disabled firewall (CVE-2006-1242, low)

  - a minor info leak in socket option handling in the     network code (CVE-2006-1343, low)

  - a flaw in IPv4 netfilter handling for the unlikely use     of SNMP NAT processing that allowed a remote user to     cause a denial of service (crash) or potential memory     corruption (CVE-2006-2444, moderate)

Note: The kernel-unsupported package contains various drivers and modules that are unsupported and therefore might contain security problems that have not been addressed.

All Red Hat Enterprise Linux 3 users are advised to upgrade their kernels to the packages associated with their machine architectures and configurations as listed in this erratum.

Updated kernel packages that fix a number of security issues as well as other bugs are now available for Red Hat Enterprise Linux 2.1 (32 bit architectures)

This security advisory has been rated as having important security impact by the Red Hat Security Response Team.

The Linux kernel handles the basic functions of the operating system.

These new kernel packages contain fixes for the security issues described below :

* a flaw in the USB devio handling of device removal that allowed a local user to cause a denial of service (crash) (CVE-2005-3055, moderate)

* a flaw in ROSE due to missing verification of the ndigis argument of new routes (CVE-2005-3273, moderate)

* an info leak on AMD-based x86 systems that allowed a local user to retrieve the floating point exception state of a process run by a different user (CVE-2006-1056, important)

* a minor info leak in socket name handling in the network code (CVE-2006-1342, low)

* a minor info leak in socket option handling in the network code (CVE-2006-1343, low)

* a directory traversal vulnerability in smbfs that allowed a local user to escape chroot restrictions for an SMB-mounted filesystem via '..\\' sequences (CVE-2006-1864, moderate)

* a flaw in the mprotect system call that allowed to give write permission to a readonly attachment of shared memory (CVE-2006-2071, moderate)

A performance bug in the NFS implementation that caused clients to frequently pause when sending TCP segments during heavy write loads was also addressed.

All Red Hat Enterprise Linux 2.1 users are advised to upgrade their kernels to these updated packages, which contain backported fixes to correct these issues.

This update includes a number of security issues that have been fixed upstream over the last week or so.

i386/x86-64: Fix x87 information leak between processes (CVE-2006-1056) ip_route_input panic fix (CVE-2006-1525) fix MADV_REMOVE vulnerability (CVE-2006-1524) shmat: stop mprotect from giving write permission to a readonly attachment (CVE-2006-1524) Fix MPBL0010 driver insecure sysfs permissions x86_64: When user could have changed RIP always force IRET (CVE-2006-0744) Fix RCU signal handling Keys: Fix oops when adding key to non-keyring (CVE-2006-1522) sysfs: zero terminate sysfs write buffers (CVE-2006-1055)

It also includes various other fixes from the -stable tree. Full changelogs are available from :

http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.16.9 http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.16.8 http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.16.7 http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.16.6 http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.16.5 http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.16.4 http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.16.3 http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.16.2

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
79511	OracleVM 3.1 : xen (OVMSA-2013-0043)	Nessus	OracleVM Local Security Checks	medium
79510	OracleVM 3.2 : xen (OVMSA-2013-0042)	Nessus	OracleVM Local Security Checks	medium
27877	Ubuntu 5.04 / 5.10 / 6.06 LTS : linux-source-2.6.10/2.6.12/2.6.15 vulnerabilities (USN-302-1)	Nessus	Ubuntu Local Security Checks	high
22645	Debian DSA-1103-1 : kernel-source-2.6.8 - several vulnerabilities	Nessus	Debian Local Security Checks	critical
22639	Debian DSA-1097-1 : kernel-source-2.4.27 - several vulnerabilities	Nessus	Debian Local Security Checks	critical
22276	CentOS 4 : kernel (CESA-2006:0575)	Nessus	CentOS Local Security Checks	high
22221	RHEL 4 : kernel (RHSA-2006:0575)	Nessus	Red Hat Local Security Checks	high
22135	CentOS 3 : kernel (CESA-2006:0437)	Nessus	CentOS Local Security Checks	high
22086	RHEL 3 : kernel (RHSA-2006:0437)	Nessus	Red Hat Local Security Checks	high
22054	RHEL 2.1 : kernel (RHSA-2006:0579)	Nessus	Red Hat Local Security Checks	medium
21253	Fedora Core 4 : kernel-2.6.16-1.2096_FC4 (2006-423)	Nessus	Fedora Local Security Checks	medium

Detections

Analytics

CVE-2006-1056

medium

Tenable Plugins

low

high

medium

medium

high

critical

critical

high

high

high

high

medium

medium