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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2010:040
        Date:                   Mon, 13 Sep 2010 15:00:00 +0000
        Affected Products:      SUSE Linux Enterprise High Availability Extension 11 SP1
                                SUSE Linux Enterprise Desktop 11 SP1
                                SUSE Linux Enterprise Server 11 SP1
        Vulnerability Type:     remote denial of service
        CVSS v2 Base Score:     10.0 (AV:N/AC:L/Au:N/C:C/I:C/A:C)
        SUSE Default Package:   yes
        Cross-References:       CVE-2010-2478, CVE-2010-2521, CVE-2010-2524
                                CVE-2010-2537, CVE-2010-2538, CVE-2010-2798
                                CVE-2010-2803, CVE-2010-2942, CVE-2010-2946
                                CVE-2010-2959, CVE-2010-3015

    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 SUSE Linux Enterprise 11 Service Pack 1 kernel update contains
   various security fixes and lots of other bugfixes.

   Notable larger bugfixes and changes:
   - 603464: Fix system freeze when doing a network crash dump with a
     netxen_nic driver
   - 610828: Avoid kernel failure on connects/disconnects to a novell
     server with Novell Client 2.0
   - 612009: Fix Oracle issues due to problems with OCFS
   - 614332: Fix SMB processes stuck in interruptible sleep when using
     (LVS/ClusteredIP) + CTDB + OCFS2
   - 619525: Fix igb driver regression
   - 626321: Add patch for Apparent OCFS2 corruption after removing a
     bunch of reflinks
   - 627518: Avoid System hangs up after failed to copy files from
     smb server
   - 629552: Skip Tape rewind during boot or a scsi scan

   Following security issues were fixed:
   CVE-2010-2478: insufficient range checks on the ETHTOOL_GRXCLSRLALL
   command allowed local users to at least crash the kernel

   CVE-2010-2521: Specially crafted NFS write requests could crash
   the kernel.

   CVE-2010-2524: a malicious local user could fill the cache used by
   CIFS do perform dns lookups with chosen data, therefore tricking the
   kernel into mounting a wrong CIFS server.

   CVE-2010-2537: a local user could overwrite append-only files on a
   btrfs file system

   CVE-2010-2538: a local user could read kernel memory of a btrfs
   file system

   CVE-2010-2798: local users could trigger a NULL dereference via gfs2
   file system

   CVE-2010-2803: driver specific drm ioctl could leak kernel memory to
   users with access to dri devices

   CVE-2010-2942: 'tc dump' could leak some kernel memory

   CVE-2010-2946: the 'os2' xattr namespace could be used to bypass
   xattr namespace rules

   CVE-2010-2959: integer overflows in the CAN subsystem allowed attackers   to crash the kernel or gain privileges

   CVE-2010-3015: certain write operations on an ext4 filesystem could
   crash the kernel

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 Server 11 SP1
     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

   SUSE Linux Enterprise Desktop 11 SP1
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise High Availability Extension 11 SP1
     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:

   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: 2010-040: Linux kernel Security Update

September 13, 2010
This SUSE Linux Enterprise 11 Service Pack 1 kernel update contains This SUSE Linux Enterprise 11 Service Pack 1 kernel update contains various security fixes and lots of other bug...

Summary


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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2010:040
        Date:                   Mon, 13 Sep 2010 15:00:00 +0000
        Affected Products:      SUSE Linux Enterprise High Availability Extension 11 SP1
                                SUSE Linux Enterprise Desktop 11 SP1
                                SUSE Linux Enterprise Server 11 SP1
        Vulnerability Type:     remote denial of service
        CVSS v2 Base Score:     10.0 (AV:N/AC:L/Au:N/C:C/I:C/A:C)
        SUSE Default Package:   yes
        Cross-References:       CVE-2010-2478, CVE-2010-2521, CVE-2010-2524
                                CVE-2010-2537, CVE-2010-2538, CVE-2010-2798
                                CVE-2010-2803, CVE-2010-2942, CVE-2010-2946
                                CVE-2010-2959, CVE-2010-3015

    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 SUSE Linux Enterprise 11 Service Pack 1 kernel update contains
   various security fixes and lots of other bugfixes.

   Notable larger bugfixes and changes:
   - 603464: Fix system freeze when doing a network crash dump with a
     netxen_nic driver
   - 610828: Avoid kernel failure on connects/disconnects to a novell
     server with Novell Client 2.0
   - 612009: Fix Oracle issues due to problems with OCFS
   - 614332: Fix SMB processes stuck in interruptible sleep when using
     (LVS/ClusteredIP) + CTDB + OCFS2
   - 619525: Fix igb driver regression
   - 626321: Add patch for Apparent OCFS2 corruption after removing a
     bunch of reflinks
   - 627518: Avoid System hangs up after failed to copy files from
     smb server
   - 629552: Skip Tape rewind during boot or a scsi scan

   Following security issues were fixed:
   CVE-2010-2478: insufficient range checks on the ETHTOOL_GRXCLSRLALL
   command allowed local users to at least crash the kernel

   CVE-2010-2521: Specially crafted NFS write requests could crash
   the kernel.

   CVE-2010-2524: a malicious local user could fill the cache used by
   CIFS do perform dns lookups with chosen data, therefore tricking the
   kernel into mounting a wrong CIFS server.

   CVE-2010-2537: a local user could overwrite append-only files on a
   btrfs file system

   CVE-2010-2538: a local user could read kernel memory of a btrfs
   file system

   CVE-2010-2798: local users could trigger a NULL dereference via gfs2
   file system

   CVE-2010-2803: driver specific drm ioctl could leak kernel memory to
   users with access to dri devices

   CVE-2010-2942: 'tc dump' could leak some kernel memory

   CVE-2010-2946: the 'os2' xattr namespace could be used to bypass
   xattr namespace rules

   CVE-2010-2959: integer overflows in the CAN subsystem allowed attackers   to crash the kernel or gain privileges

   CVE-2010-3015: certain write operations on an ext4 filesystem could
   crash the kernel

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 Server 11 SP1
     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

   SUSE Linux Enterprise Desktop 11 SP1
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise High Availability Extension 11 SP1
     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:

   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