SUSE 10 SP2: 2009-028 Critical: Kernel Remote Code Execution Advisory

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

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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2009:028
        Date:                   Wed, 20 May 2009 18: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:     potential remote code execution
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       CVE-2009-0834, CVE-2009-0835, CVE-2009-0859
                                CVE-2009-1072, CVE-2009-1265, CVE-2009-1337
                                CVE-2009-1439

    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:
            See SUSE Security Summary Report.
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   The Linux kernel on SUSE Linux Enterprise 10 Service Pack 2 was
   updated to fix various security issues and several bugs.

   Following security issues were fixed:

   CVE-2009-0834: The audit_syscall_entry function in the Linux kernel
   on the x86_64 platform did not properly handle (1) a 32-bit process
   making a 64-bit syscall or (2) a 64-bit process making a 32-bit
   syscall, which allows local users to bypass certain syscall audit
   configurations via crafted syscalls.


   CVE-2009-1072: nfsd in the Linux kernel did not drop the CAP_MKNOD
   capability before handling a user request in a thread, which allows
   local users to create device nodes, as demonstrated on a filesystem
   that has been exported with the root_squash option.


   CVE-2009-0835: The __secure_computing function in kernel/seccomp.c
   in the seccomp subsystem in the Linux kernel on the x86_64 platform,
   when CONFIG_SECCOMP is enabled, does not properly handle (1) a 32-bit
   process making a 64-bit syscall or (2) a 64-bit process making a
   32-bit syscall, which allows local users to bypass intended access
   restrictions via crafted syscalls that are misinterpreted as (a)
   stat or (b) chmod.


   CVE-2009-1439: Buffer overflow in fs/cifs/connect.c in CIFS in the
   Linux kernel 2.6.29 and earlier allows remote attackers to cause
   a denial of service (crash) or potential code execution via a long
   nativeFileSystem field in a Tree Connect response to an SMB mount
   request.

   This requires that kernel can be made to mount a "cifs" filesystem from a
   malicious CIFS server.


   CVE-2009-1337: The exit_notify function in kernel/exit.c in the Linux
   kernel did not restrict exit signals when the CAP_KILL capability
   is held, which allows local users to send an arbitrary signal to a
   process by running a program that modifies the exit_signal field and
   then uses an exec system call to launch a setuid application.

   CVE-2009-0859: The shm_get_stat function in ipc/shm.c in the shm
   subsystem in the Linux kernel, when CONFIG_SHMEM is disabled,
   misinterprets the data type of an inode, which allows local users   to cause a denial of service (system hang) via an SHM_INFO shmctl
   call, as demonstrated by running the ipcs program. (SUSE is enabling
   CONFIG_SHMEM, so is by default not affected, the fix is just for
   completeness).

   The GCC option -fwrapv has been added to compilation to work around
   potentially removing integer overflow checks.

   CVE-2009-1265: Integer overflow in rose_sendmsg (sys/net/af_rose.c) in
   the Linux kernel might allow attackers to obtain sensitive information
   via a large length value, which causes "garbage" memory to be sent.

   Also a number of bugs were fixed, for details please see the RPM
   changelog.

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.

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 10 SP2 DEBUGINFO for IPF
     

   SUSE Linux Enterprise Server 10 SP2
     
     
     
     
     

   SLE SDK 10 SP2
     
     
     
     

   SUSE Linux Enterprise 10 SP2 DEBUGINFO
     
     
     
     

   SUSE Linux Enterprise Desktop 10 SP2
     
     

   SUSE Linux Enterprise Desktop 10 SP2 for x86
     

______________________________________________________________________________

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

   See SUSE Security Summary Report.
______________________________________________________________________________

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