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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2011:005
        Date:                   Tue, 25 Jan 2011 11:00:00 +0000
        Affected Products:      SLE SDK 10 SP3
                                SUSE Linux Enterprise Desktop 10 SP3
                                SUSE Linux Enterprise Server 10 SP3
        Vulnerability Type:     local privilege escalation
        CVSS v2 Base Score:     7.2 (AV:L/AC:L/Au:N/C:C/I:C/A:C)
        SUSE Default Package:   yes
        Cross-References:       CVE-2010-3699, CVE-2010-3848, CVE-2010-3849
                                CVE-2010-3850, CVE-2010-4160, CVE-2010-4258

    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 SP3 kernel fixes
   several security issues and bugs.

   Following security issues were fixed:
   CVE-2010-4258: A local attacker could use a Oops (kernel crash) caused
   by other flaws to write a 0 byte to a attacker controlled address
   in the kernel. This could lead to privilege escalation together with
   other issues.

   CVE-2010-3699: The backend driver in Xen 3.x allows guest OS users to
   cause a denial of service via a kernel thread leak, which prevents the
   device and guest OS from being shut down or create a zombie domain,
   causes a hang in zenwatch, or prevents unspecified xm commands from
   working properly, related to (1) netback, (2) blkback, or (3) blktap.

   CVE-2010-3849: The econet_sendmsg function in net/econet/af_econet.c
   in the Linux kernel, when an econet address is configured, allowed
   local users to cause a denial of service (NULL pointer dereference
   and OOPS) via a sendmsg call that specifies a NULL value for the
   remote address field.

   CVE-2010-3848: Stack-based buffer overflow in the econet_sendmsg
   function in net/econet/af_econet.c in the Linux kernel when an econet
   address is configured, allowed local users to gain privileges by
   providing a large number of iovec structures.

   CVE-2010-3850: The ec_dev_ioctl function in net/econet/af_econet.c
   in the Linux kernel did not require the CAP_NET_ADMIN capability,
   which allowed local users to bypass intended access restrictions and
   configure econet addresses via an SIOCSIFADDR ioctl call.

   CVE-2010-4160: An overflow in sendto() and recvfrom() routines was
   fixed that could be used by local attackers to potentially crash the
   kernel using some socket families like L2TP.

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 SP3 for AMD64 and Intel EM64T
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Server 10 SP3
     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 SP3
     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 SP3
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Desktop 10 SP3 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-005: Linux kernel Security Update

January 25, 2011
This kernel update for the SUSE Linux Enterprise 10 SP3 kernel fixes This kernel update for the SUSE Linux Enterprise 10 SP3 kernel fixes several security issues and bugs

Summary


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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2011:005
        Date:                   Tue, 25 Jan 2011 11:00:00 +0000
        Affected Products:      SLE SDK 10 SP3
                                SUSE Linux Enterprise Desktop 10 SP3
                                SUSE Linux Enterprise Server 10 SP3
        Vulnerability Type:     local privilege escalation
        CVSS v2 Base Score:     7.2 (AV:L/AC:L/Au:N/C:C/I:C/A:C)
        SUSE Default Package:   yes
        Cross-References:       CVE-2010-3699, CVE-2010-3848, CVE-2010-3849
                                CVE-2010-3850, CVE-2010-4160, CVE-2010-4258

    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 SP3 kernel fixes
   several security issues and bugs.

   Following security issues were fixed:
   CVE-2010-4258: A local attacker could use a Oops (kernel crash) caused
   by other flaws to write a 0 byte to a attacker controlled address
   in the kernel. This could lead to privilege escalation together with
   other issues.

   CVE-2010-3699: The backend driver in Xen 3.x allows guest OS users to
   cause a denial of service via a kernel thread leak, which prevents the
   device and guest OS from being shut down or create a zombie domain,
   causes a hang in zenwatch, or prevents unspecified xm commands from
   working properly, related to (1) netback, (2) blkback, or (3) blktap.

   CVE-2010-3849: The econet_sendmsg function in net/econet/af_econet.c
   in the Linux kernel, when an econet address is configured, allowed
   local users to cause a denial of service (NULL pointer dereference
   and OOPS) via a sendmsg call that specifies a NULL value for the
   remote address field.

   CVE-2010-3848: Stack-based buffer overflow in the econet_sendmsg
   function in net/econet/af_econet.c in the Linux kernel when an econet
   address is configured, allowed local users to gain privileges by
   providing a large number of iovec structures.

   CVE-2010-3850: The ec_dev_ioctl function in net/econet/af_econet.c
   in the Linux kernel did not require the CAP_NET_ADMIN capability,
   which allowed local users to bypass intended access restrictions and
   configure econet addresses via an SIOCSIFADDR ioctl call.

   CVE-2010-4160: An overflow in sendto() and recvfrom() routines was
   fixed that could be used by local attackers to potentially crash the
   kernel using some socket families like L2TP.

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 SP3 for AMD64 and Intel EM64T
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Server 10 SP3
     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 SP3
     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 SP3
     https://login.microfocus.com/nidp/app/login
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Desktop 10 SP3 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