SUSE Linux Enterprise 10 SP2: 2009-054 Moderate Local Escalation Risk

Warning: Undefined array key "advisoryid" in /var/www/www.linuxsecurity.com-443/html/tmp/regularlabs/custom_php/3629835_1edcd913e2b52798c5b9126b8927230e on line 19

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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2009:054
        Date:                   Wed, 11 Nov 2009 15:00:00 +0000
        Affected Products:      SLE SDK 10 SP2
                                SUSE Linux Enterprise Desktop 10 SP2
                                SUSE Linux Enterprise 10 SP2 DEBUGINFO
                                SUSE Linux Enterprise Server 10 SP2
        Vulnerability Type:     local privilege escalation
        Severity (1-10):        7
        SUSE Default Package:   yes
        Cross-References:       CVE-2009-1192, CVE-2009-1633, CVE-2009-2848
                                CVE-2009-2909, CVE-2009-2910, CVE-2009-3002
                                CVE-2009-3238, CVE-2009-3547

    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:
            - Pending kernels for CVE-2009-3547
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   This update fixes a several security issues and various bugs in the
   SUSE Linux Enterprise 10 SP 2 kernel.

   Following security issues were fixed:
   CVE-2009-3547: A race condition during pipe open could be used by
   local attackers to elevate privileges.

   CVE-2009-2910: On x86_64 systems an information leak of high register
   contents (upper 32bit) was fixed.

   CVE-2009-3238: The randomness of the ASLR methods used in the kernel
   was increased.

   CVE-2009-1192: A information leak from the kernel due to uninitialized
   memory in AGP handling was fixed.

   CVE-2009-2909: A signed comparison in the ax25 sockopt handler
   was fixed which could be used to crash the kernel or potentially
   execute code.

   CVE-2009-2848: The execve function in the Linux kernel did not properly
   clear the current->clear_child_tid pointer, which allows local
   users to cause a denial of service (memory corruption) or possibly
   gain privileges via a clone system call with CLONE_CHILD_SETTID or
   CLONE_CHILD_CLEARTID enabled, which is not properly handled during
   thread creation and exit.

   CVE-2009-3002: Fixed various socket handler getname leaks, which
   could disclose memory previously used by the kernel or other userland
   processes to the local attacker.

   CVE-2009-1633: Multiple buffer overflows in the cifs subsystem in the
   Linux kernel allow remote CIFS servers to cause a denial of service
   (memory corruption) and possibly have unspecified other impact via (1)
   a malformed Unicode string, related to Unicode string area alignment
   in fs/cifs/sess.c; or (2) long Unicode characters, related to
   fs/cifs/cifssmb.c and the cifs_readdir function in fs/cifs/readdir.c.

   Also see the RPM changelog for more changes.

2) Solution or Work-Around

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

3) Special Instructions and Notes

   Reboot the machine after installing the update.

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   Online Update (YOU) tool. YOU detects which updates are required and
   automatically performs 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:

   SUSE Linux Enterprise Desktop 10 SP2 for AMD64 and Intel EM64T
     

   SUSE Linux Enterprise 10 SP2 DEBUGINFO for IBM zSeries 64bit
     

   SUSE Linux Enterprise 10 SP2 DEBUGINFO for IBM POWER
     

   SUSE Linux Enterprise Desktop 10 SP2
     
     

   SUSE Linux Enterprise Desktop 10 SP2 for x86
     

   SUSE Linux Enterprise Server 10 SP2
     
     
     
     
     

   SLE SDK 10 SP2
     
     
     
     

   SUSE Linux Enterprise 10 SP2 DEBUGINFO
     
     
     
     

   SUSE Linux Enterprise 10 SP2 DEBUGINFO for IPF
     

______________________________________________________________________________

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

   - Pending kernels for CVE-2009-3547 problem
     SUSE Linux Enterprise 10 SP3 kernels will be released tomorrow.

     SUSE Linux Enterprise 9 kernels had another QA failure and so will
     be released approximately begin of next week.

     openSUSE 11.0, 11.1 and SUSE Linux Enterprise 11 kernels have
     "mmap_min_addr" protection by default and will be released in their
     regular release cycles. (Probably around end of November).

______________________________________________________________________________

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