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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2011:026
        Date:                   Fri, 20 May 2011 10:00:00 +0000
        Affected Products:      SUSE Linux Enterprise Desktop 10 SP4
                                SLE SDK 10 SP4
                                SUSE Linux Enterprise Server 10 SP4
        Vulnerability Type:     remote denial of service
        CVSS v2 Base Score:     7.9 (AV:A/AC:M/Au:N/C:C/I:C/A:C)
        SUSE Default Package:   no
        Cross-References:       CVE-2010-0008, CVE-2010-4251, CVE-2011-0191
                                CVE-2011-1010, CVE-2011-1012, CVE-2011-1016
                                CVE-2011-1017, CVE-2011-1160, CVE-2011-1163
                                CVE-2011-1180, CVE-2011-1182, CVE-2011-1476
                                CVE-2011-1477, CVE-2011-1493, CVE-2011-1573
                                CVE-2011-1577, CVE-2011-1585

    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

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

   Following security issues were fixed:
   CVE-2011-1017,CVE-2011-1012: 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-1573: Bounds checking was missing in AARESOLVE_OFFSET, which
   allowed local attackers to overwrite kernel memory and so escalate
   privileges or crash the kernel.

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

   CVE-2011-1160: Kernel information via the TPM devices could by used
   by local attackers to read kernel memory.

   CVE-2011-1577: The Linux kernel automatically evaluated partition
   tables of storage devices. The code for evaluating EFI GUID partitions
   (in fs/partitions/efi.c) contained a bug that causes a kernel oops
   on certain corrupted GUID partition tables, which might be used by
   local attackers to crash the kernel or potentially execute code.

   CVE-2011-1180: In the IrDA module, length fields provided by a peer
   for names and attributes may be longer than the destination array
   sizes and were not checked, this allowed local attackers (close to
   the irda port) to potentially corrupt memory.

   CVE-2010-4251: A system out of memory condition (denial of service)
   could be triggered with a large socket backlog, exploitable by
   local users.  This has been addressed by backlog limiting.

   CVE-2011-1016: The Radeon GPU drivers in the Linux kernel did not
   properly validate data related to the AA resolve registers, which
   allowed local users to write to arbitrary memory locations associated
   with (1) Video RAM (aka VRAM) or (2) the Graphics Translation Table
   (GTT) via crafted values.

   CVE-2011-1493: When parsing the FAC_NATIONAL_DIGIS facilities field,
   it was possible for a remote host to provide more digipeaters than
   expected, resulting in heap corruption.

   CVE-2011-1182: Local attackers could send signals to their programs
   that looked like coming from the kernel, potentially gaining privileges
   in the context of setuid programs.

   CVE-2011-1010: The code for evaluating Mac partitions (in
   fs/partitions/mac.c) contained a bug that could crash the kernel for
   certain corrupted Mac partitions.

   CVE-2011-1163: The code for evaluating OSF partitions (in
   fs/partitions/osf.c) contained a bug that leaks data from kernel heap
   memory to userspace for certain corrupted OSF partitions.

   CVE-2011-1476: Specially crafted requests may be written to
   /dev/sequencer resulting in an underflow when calculating a size for a
   copy_from_user() operation in the driver for MIDI interfaces. On x86,
   this just returns an error, but it could have caused memory corruption
   on other architectures. Other malformed requests could have resulted
   in the use of uninitialized variables.

   CVE-2011-1477: Due to a failure to validate user-supplied indexes in
   the driver for Yamaha YM3812 and OPL-3 chips, a specially crafted
   ioctl request could have been sent to /dev/sequencer, resulting in
   reading and writing beyond the bounds of heap buffers, and potentially
   allowing privilege escalation.

   CVE-2011-0191: A information leak in the XFS geometry calls could be
   used by local attackers to gain access to kernel information.

   CVE-2010-0008: The sctp_rcv_ootb function in the SCTP implementation
   in the Linux kernel allowed remote attackers to cause a denial of
   service (infinite loop) via (1) an Out Of The Blue (OOTB) chunk or
   (2) a chunk of zero length.

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" 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:

   SUSE Linux Enterprise Desktop 10 SP4 for AMD64 and Intel EM64T
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Server 10 SP4
     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

   SLE SDK 10 SP4
     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 Desktop 10 SP4
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Desktop 10 SP4 for x86
     https://login.microfocus.com/nidp/app/login

______________________________________________________________________________

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

SuSE: 2011-026: Linux kernel Security Update

May 20, 2011
This kernel update for the SUSE Linux Enterprise 10 SP4 kernel fixes This kernel update for the SUSE Linux Enterprise 10 SP4 kernel fixes several security issues and bugs

Summary


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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2011:026
        Date:                   Fri, 20 May 2011 10:00:00 +0000
        Affected Products:      SUSE Linux Enterprise Desktop 10 SP4
                                SLE SDK 10 SP4
                                SUSE Linux Enterprise Server 10 SP4
        Vulnerability Type:     remote denial of service
        CVSS v2 Base Score:     7.9 (AV:A/AC:M/Au:N/C:C/I:C/A:C)
        SUSE Default Package:   no
        Cross-References:       CVE-2010-0008, CVE-2010-4251, CVE-2011-0191
                                CVE-2011-1010, CVE-2011-1012, CVE-2011-1016
                                CVE-2011-1017, CVE-2011-1160, CVE-2011-1163
                                CVE-2011-1180, CVE-2011-1182, CVE-2011-1476
                                CVE-2011-1477, CVE-2011-1493, CVE-2011-1573
                                CVE-2011-1577, CVE-2011-1585

    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

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

   Following security issues were fixed:
   CVE-2011-1017,CVE-2011-1012: 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-1573: Bounds checking was missing in AARESOLVE_OFFSET, which
   allowed local attackers to overwrite kernel memory and so escalate
   privileges or crash the kernel.

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

   CVE-2011-1160: Kernel information via the TPM devices could by used
   by local attackers to read kernel memory.

   CVE-2011-1577: The Linux kernel automatically evaluated partition
   tables of storage devices. The code for evaluating EFI GUID partitions
   (in fs/partitions/efi.c) contained a bug that causes a kernel oops
   on certain corrupted GUID partition tables, which might be used by
   local attackers to crash the kernel or potentially execute code.

   CVE-2011-1180: In the IrDA module, length fields provided by a peer
   for names and attributes may be longer than the destination array
   sizes and were not checked, this allowed local attackers (close to
   the irda port) to potentially corrupt memory.

   CVE-2010-4251: A system out of memory condition (denial of service)
   could be triggered with a large socket backlog, exploitable by
   local users.  This has been addressed by backlog limiting.

   CVE-2011-1016: The Radeon GPU drivers in the Linux kernel did not
   properly validate data related to the AA resolve registers, which
   allowed local users to write to arbitrary memory locations associated
   with (1) Video RAM (aka VRAM) or (2) the Graphics Translation Table
   (GTT) via crafted values.

   CVE-2011-1493: When parsing the FAC_NATIONAL_DIGIS facilities field,
   it was possible for a remote host to provide more digipeaters than
   expected, resulting in heap corruption.

   CVE-2011-1182: Local attackers could send signals to their programs
   that looked like coming from the kernel, potentially gaining privileges
   in the context of setuid programs.

   CVE-2011-1010: The code for evaluating Mac partitions (in
   fs/partitions/mac.c) contained a bug that could crash the kernel for
   certain corrupted Mac partitions.

   CVE-2011-1163: The code for evaluating OSF partitions (in
   fs/partitions/osf.c) contained a bug that leaks data from kernel heap
   memory to userspace for certain corrupted OSF partitions.

   CVE-2011-1476: Specially crafted requests may be written to
   /dev/sequencer resulting in an underflow when calculating a size for a
   copy_from_user() operation in the driver for MIDI interfaces. On x86,
   this just returns an error, but it could have caused memory corruption
   on other architectures. Other malformed requests could have resulted
   in the use of uninitialized variables.

   CVE-2011-1477: Due to a failure to validate user-supplied indexes in
   the driver for Yamaha YM3812 and OPL-3 chips, a specially crafted
   ioctl request could have been sent to /dev/sequencer, resulting in
   reading and writing beyond the bounds of heap buffers, and potentially
   allowing privilege escalation.

   CVE-2011-0191: A information leak in the XFS geometry calls could be
   used by local attackers to gain access to kernel information.

   CVE-2010-0008: The sctp_rcv_ootb function in the SCTP implementation
   in the Linux kernel allowed remote attackers to cause a denial of
   service (infinite loop) via (1) an Out Of The Blue (OOTB) chunk or
   (2) a chunk of zero length.

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" 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:

   SUSE Linux Enterprise Desktop 10 SP4 for AMD64 and Intel EM64T
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Server 10 SP4
     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

   SLE SDK 10 SP4
     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 Desktop 10 SP4
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Desktop 10 SP4 for x86
     https://login.microfocus.com/nidp/app/login

______________________________________________________________________________

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

References

Severity

Related News