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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2010:019
        Date:                   Tue, 30 Mar 2010 10:00:00 +0000
        Affected Products:      SLE SDK 10 SP3
                                SUSE Linux Enterprise Desktop 10 SP3
                                SUSE Linux Enterprise Server 10 SP3
        Vulnerability Type:     remote denial of service
        CVSS v2 Base Score:     7.8 (AV:N/AC:L/Au:N/C:N/I:N/A:C)
        SUSE Default Package:   yes
        Cross-References:       CVE-2009-3556, CVE-2009-4020, CVE-2010-0410
                                CVE-2010-1083, CVE-2010-1086, CVE-2010-1088

    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 update fixes lots of bugs and some security issues in the SUSE
   Linux Enterprise 10 SP 3 kernel.

   CVE-2009-4020: Stack-based buffer overflow in the hfs subsystem in the
   Linux kernel allows remote attackers to have an unspecified impact
   via a crafted Hierarchical File System (HFS) filesystem, related to
   the hfs_readdir function in fs/hfs/dir.c.

   CVE-2010-0410: drivers/connector/connector.c in the Linux kernel
   allows local users to cause a denial of service (memory consumption and
   system crash) by sending the kernel many NETLINK_CONNECTOR messages.

   CVE-2009-3556: A configuration value in the qla2xxx driver in the
   Linux kernel when N_Port ID Virtualization (NPIV) hardware is used,
   sets world-writable permissions for the (1) vport_create and (2)
   vport_delete files under /sys/class/scsi_host/, which allows local
   users to make arbitrary changes to SCSI host attributes by modifying
   these files.

   CVE-2010-1083: A kernel information leak using user space USB devices
   could be used by local attackers with USB access to read recently
   freed kernel memory.

   CVE-2010-1086: A ULE decapsulation denial of service problem in DVB
   drivers was fixed that could be triggered by invalid DVB data packets.

   CVE-2010-1088: A NFS denial of service by following "automount"
   symlinks was fixed.

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 SP3 for AMD64 and Intel EM64T
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=30110847005ad3a7ea7c5d1efd067ce1

   SUSE Linux Enterprise Server 10 SP3
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=30110847005ad3a7ea7c5d1efd067ce1
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=d5a23ca2612948125ba212f86484077b
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=9a1d7bed362eab0ffb8a1cfcb944439e
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=ffb169f8e0b809058bff6cb318c6a511
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=44be42f54c5e35e6e551e68351bbd0e1

   SLE SDK 10 SP3
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=30110847005ad3a7ea7c5d1efd067ce1
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=9a1d7bed362eab0ffb8a1cfcb944439e
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=ffb169f8e0b809058bff6cb318c6a511
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=44be42f54c5e35e6e551e68351bbd0e1

   SUSE Linux Enterprise Desktop 10 SP3
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=30110847005ad3a7ea7c5d1efd067ce1
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=44be42f54c5e35e6e551e68351bbd0e1

   SUSE Linux Enterprise Desktop 10 SP3 for x86
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=44be42f54c5e35e6e551e68351bbd0e1

______________________________________________________________________________

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