-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2011:040
        Date:                   Tue, 20 Sep 2011 16:00:00 +0000
        Affected Products:      SLE SDK 10 SP3
                                SUSE Linux Enterprise Server 10 SP3
        Vulnerability Type:     remote denial of service
        CVSS v2 Base Score:     7.8 (AV:N/AC:L/Au:N/C:N/I:N/A:C)
        SUSE Default Package:   yes
        Cross-References:       CVE-2011-0726, CVE-2011-1017, CVE-2011-1093
                                CVE-2011-1585, CVE-2011-1745, CVE-2011-1746
                                CVE-2011-1776, CVE-2011-2022, CVE-2011-2182
                                CVE-2011-2491, CVE-2011-2496, CVE-2011-3191

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             Linux kernel security update
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            none
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   This kernel update for the SUSE Linux Enterprise 10 SP3 kernel fixes
   several security issues and bugs.

   Following security issues were fixed:
   CVE-2011-3191: A signedness issue in CIFS could possibly have lead
   to to memory corruption, if a malicious server could send crafted
   replies to the host.

   CVE-2011-1776: Timo Warns reported an issue in the Linux implementation
   for GUID partitions. Users with physical access could gain access to
   sensitive kernel memory by adding a storage device with a specially
   crafted corrupted invalid partition table.

   CVE-2011-1093: The dccp_rcv_state_process function in net/dccp/input.c
   in the Datagram Congestion Control Protocol (DCCP) implementation
   in the Linux kernel did not properly handle packets for a CLOSED
   endpoint, which allowed remote attackers to cause a denial of service
   (NULL pointer dereference and OOPS) by sending a DCCP-Close packet
   followed by a DCCP-Reset packet.

   CVE-2011-1745: Integer overflow in the agp_generic_insert_memory
   function in drivers/char/agp/generic.c in the Linux kernel allowed
   local users to gain privileges or cause a denial of service (system
   crash) via a crafted AGPIOC_BIND agp_ioctl ioctl call.

   CVE-2011-1746: Multiple integer overflows in the (1)
   agp_allocate_memory and (2) agp_create_user_memory functions in
   drivers/char/agp/generic.c in the Linux kernel allowed local users to
   trigger buffer overflows, and consequently cause a denial of service
   (system crash) or possibly have unspecified other impact, via vectors   related to calls that specify a large number of memory pages.

   CVE-2011-2022: The agp_generic_remove_memory function in
   drivers/char/agp/generic.c in the Linux kernel before 2.6.38.5 did
   not validate a certain start parameter, which allowed local users   to gain privileges or cause a denial of service (system crash) via a
   crafted AGPIOC_UNBIND agp_ioctl ioctl call, a different vulnerability
   than CVE-2011-1745.

   CVE-2011-0726: The do_task_stat function in fs/proc/array.c in the
   Linux kernel did not perform an expected uid check, which made it
   easier for local users to defeat the ASLR protection mechanism by
   reading the start_code and end_code fields in the /proc/#####/stat
   file for a process executing a PIE binary.

   CVE-2011-2496: The normal mmap paths all avoid creating a mapping
   where the pgoff inside the mapping could wrap around due to
   overflow. However, an expanding mremap() can take such a non-wrapping
   mapping and make it bigger and cause a wrapping condition.

   CVE-2011-2491: A local unprivileged user able to access a NFS
   filesystem could use file locking to deadlock parts of an nfs server
   under some circumstance.

   CVE-2011-1017,CVE-2011-2182: The code for evaluating LDM partitions
   (in fs/partitions/ldm.c) contained bugs that could crash the kernel
   for certain corrupted LDM partitions.

   CVE-2011-1585: When using a setuid root mount.cifs, local users could
   hijack password protected mounted CIFS shares of other local users.


   Also following non-security bugs were fixed:
   - patches.suse/fs-proc-vmcorec-add-hook-to-read_from_oldmem-to-check-for-non-ram-pages.patch:
   fs/proc/vmcore.c: add hook to read_from_oldmem() to check
   for non-ram pages (bnc#684297).
   - patches.xen/1062-xenbus-dev-leak.patch: xenbus: Fix memory leak on release.
   - patches.xen/1074-xenbus_conn-type.patch: xenbus: fix type
   inconsistency with xenbus_conn().
   - patches.xen/1080-blkfront-xenbus-gather-format.patch: blkfront: fix
   data size for xenbus_gather in connect().
   - patches.xen/1081-blkback-resize-transaction-end.patch: xenbus: fix
   xenbus_transaction_start() hang caused by double xenbus_transaction_end().
   - patches.xen/1089-blkback-barrier-check.patch: blkback: dont fail
   empty barrier requests.
   - patches.xen/1091-xenbus-dev-no-BUG.patch: xenbus: dont BUG() on user
   mode induced conditions (bnc#696107).
   - patches.xen/1098-blkfront-cdrom-ioctl-check.patch: blkfront: avoid
   NULL de-reference in CDROM ioctl handling (bnc#701355).
   - patches.xen/1102-x86-max-contig-order.patch: x86: use dynamically
   adjusted upper bound for contiguous regions (bnc#635880).
   - patches.xen/xen3-x86-sanitize-user-specified-e820-memmap-values.patch:
   x86: sanitize user specified e820 memmap values (bnc#665543).
   - patches.fixes/libiscsi-dont-run-scsi-eh-if-iscsi-task-is-making-progress:
   Fix typo, which was uncovered in debug mode.
   - patches.fixes/pacct-fix-sighand-siglock-usage.patch: Fix
   sighand->siglock usage in kernel/acct.c (bnc#705463).

2) Solution or Work-Around

   There is no known workaround, please install the update packages.

3) Special Instructions and Notes

   Please reboot the machine after installing the update.

   If you are using XEN, you also should install and boot the current
   SUSE Linux Enterprise 10 SP3 XEN update.
4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   "Online Update" module or the "zypper" commandline tool. The package and
   patch management stack will detect which updates are required and
   automatically perform the necessary steps to verify and install them.

   Alternatively, download the update packages for your distribution manually
   and verify their integrity by the methods listed in Section 6 of this
   announcement. Then install the packages using the command

     rpm -Fhv 

   to apply the update, replacing  with the filename of the
   downloaded RPM package.

   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:

   SLE SDK 10 SP3
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Server 10 SP3
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login

______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   none
______________________________________________________________________________

6) Authenticity Verification and Additional Information

  - Announcement authenticity verification:

    SUSE security announcements are published via mailing lists and on Web
    sites. The authenticity and integrity of a SUSE security announcement is
    guaranteed by a cryptographic signature in each announcement. All SUSE
    security announcements are published with a valid signature.

    To verify the signature of the announcement, save it as text into a file
    and run the command

      gpg --verify 

    replacing  with the name of the file where you saved the
    announcement. The output for a valid signature looks like:

      gpg: Signature made  using RSA key ID 3D25D3D9
      gpg: Good signature from "SuSE Security Team "

    where  is replaced by the date the document was signed.

    If the security team's key is not contained in your key ring, you can
    import it from the first installation CD. To import the key, use the
    command

      gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

  - Package authenticity verification:

    SUSE update packages are available on many mirror FTP servers all over the
    world. While this service is considered valuable and important to the free
    and open source software community, the authenticity and the integrity of
    a package needs to be verified to ensure that it has not been tampered
    with.

    The internal rpm package signatures provide an easy way to verify the
    authenticity of an RPM package. Use the command

     rpm -v --checksig 

    to verify the signature of the package, replacing  with the
    filename of the RPM package downloaded. The package is unmodified if it
    contains a valid signature from build@suse.de with the key ID 9C800ACA.

    This key is automatically imported into the RPM database (on
    RPMv4-based distributions) and the gpg key ring of 'root' during
    installation. You can also find it on the first installation CD and at
    the end of this announcement.

  - SUSE runs two security mailing lists to which any interested party may
    subscribe:

    opensuse-security@opensuse.org
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    opensuse-security-announce@opensuse.org
        -   SUSE's announce-only mailing list.
            Only SUSE's security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================