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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2010:033
        Date:                   Mon, 02 Aug 2010 10: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:     local privilege escalation
        CVSS v2 Base Score:     6.9 (AV:L/AC:M/Au:N/C:C/I:C/A:C)
        SUSE Default Package:   yes
        Cross-References:       CVE-2010-1641, CVE-2010-2066, CVE-2010-2495

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

   Notable larger bugfixes and changes:
   - The btrfs filesystem received backports of lots of fixes from 2.6.35.
   - A OCFS2 data corruption during high load was fixed.
   - A deadlock in virtual interface handling in XEN introduced by
     the last update was fixed.
   - Custom truncation length was added for authentication mechanisms
     in XFRM to enable IPv6 certification.

   Following security issues were fixed:
   Several buffer overflows in the Novell Client novfs kernel module
   could be used by local users to execute code in the kernel.

   CVE-2010-2066: On ext4 filesystems make sure the MOVE_EXT ioctl cannot
   overwrite append-only files.

   CVE-2010-2495: A oops (denial of service) caused by a NULL pointer
   dereference in the l2tp protocol was fixed.

   CVE-2010-1641: In the gfs2 filesystem, fixed permissions checking
   for the setflags ioctl().

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:

   SLE 11 SERVER Unsupported Extras
     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 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-033: Linux kernel Security Update

August 2, 2010
This SUSE Linux Enterprise 11 Service Pack 1 kernel contains various This SUSE Linux Enterprise 11 Service Pack 1 kernel contains various security fixes and lots of other bugfixes

Summary


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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2010:033
        Date:                   Mon, 02 Aug 2010 10: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:     local privilege escalation
        CVSS v2 Base Score:     6.9 (AV:L/AC:M/Au:N/C:C/I:C/A:C)
        SUSE Default Package:   yes
        Cross-References:       CVE-2010-1641, CVE-2010-2066, CVE-2010-2495

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

   Notable larger bugfixes and changes:
   - The btrfs filesystem received backports of lots of fixes from 2.6.35.
   - A OCFS2 data corruption during high load was fixed.
   - A deadlock in virtual interface handling in XEN introduced by
     the last update was fixed.
   - Custom truncation length was added for authentication mechanisms
     in XFRM to enable IPv6 certification.

   Following security issues were fixed:
   Several buffer overflows in the Novell Client novfs kernel module
   could be used by local users to execute code in the kernel.

   CVE-2010-2066: On ext4 filesystems make sure the MOVE_EXT ioctl cannot
   overwrite append-only files.

   CVE-2010-2495: A oops (denial of service) caused by a NULL pointer
   dereference in the l2tp protocol was fixed.

   CVE-2010-1641: In the gfs2 filesystem, fixed permissions checking
   for the setflags ioctl().

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:

   SLE 11 SERVER Unsupported Extras
     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 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