______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kernel
        Announcement ID:        SUSE-SA:2011:041
        Date:                   Mon, 17 Oct 2011 16: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:     denial of service
        CVSS v2 Base Score:     4.9 (AV:L/AC:L/Au:N/C:N/I:N/A:C)
        SUSE Default Package:   yes
        Cross-References:       CVE-2011-2928, CVE-2011-3191, CVE-2011-3353

    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

   The SUSE Linux Enterprise 11 Service Pack 1 kernel was updated to
   2.6.32.46 and fixes various bugs and security issues.

   Following security issues were fixed:
   CVE-2011-3191: A signedness issue in CIFS could possibly have lead
   to to memory corruption, if a malicious server could send crafted
   replies to the host.

   CVE-2011-3353: In the fuse filesystem, FUSE_NOTIFY_INVAL_ENTRY did not
   check the length of the write so the message processing could overrun
   and result in a BUG_ON() in fuse_copy_fill(). This flaw could be used
   by local users able to mount FUSE filesystems to crash the system.

   CVE-2011-2928: The befs_follow_link function in fs/befs/linuxvfs.c
   in the Linux kernel did not validate the length attribute of long
   symlinks, which allowed local users to cause a denial of service
   (incorrect pointer dereference and OOPS) by accessing a long symlink
   on a malformed Be filesystem.


   Also the following non security bugs were fixed:
   - Added a missing reset for ioc_reset_in_progress in SoftReset in the
     mtpsas driver (bnc#711969).

   - Add support for the Digi/IBM PCIe 2-port Adapter (bnc#708675).

   - Always enable MSI-X on 5709 (bnc#707737).

   - sched: fix broken SCHED_RESET_ON_FORK handling (bnc#708877).

   - sched: Fix rt_rq runtime leakage bug (bnc#707096).

   - ACPI: allow passing down C1 information if no other C-states exist.

   - KDB: turn off kdb usb support by default (bnc#694670 bnc#603804).

   - xfs: Added event tracing support.
   - xfs: fix xfs_fsblock_t tracing.

   - igb: extend maximum frame size to receive VLAN tagged frames
     (bnc#688859).

   - cfq: Do not allow queue merges for queues that have no process
     references (bnc#712929).
   - cfq: break apart merged cfqqs if they stop cooperating (bnc#712929).
   - cfq: calculate the seek_mean per cfq_queue not per cfq_io_context
     (bnc#712929).
   - cfq: change the meaning of the cfqq_coop flag (bnc#712929).
   - cfq-iosched: get rid of the coop_preempt flag (bnc#712929).
   - cfq: merge cooperating cfq_queues (bnc#712929).

   - Fix FDDI and TR config checks in ipv4 arp and LLC (bnc#715235).

   - writeback: do uninterruptible sleep in balance_dirty_pages()
     (bnc#699354 bnc#699357).
   - xfs: fix memory reclaim recursion deadlock on locked inode buffer
     (bnc#699355 bnc#699354).
   - xfs: use GFP_NOFS for page cache allocation (bnc#699355 bnc#699354).

   - virtio-net: init link state correctly (bnc#714966).

   - cpufreq: pcc-cpufreq: sanity check to prevent a NULL pointer
     dereference (bnc#709412).

   - x86: ucode-amd: Do not warn when no ucode is available for a CPU

   - patches.arch/x86_64-unwind-annotations: Refresh (bnc#588458).
   - patches.suse/stack-unwind: Refresh (bnc#588458).

   - splice: direct_splice_actor() should not use pos in sd (bnc#715763).

   - qdio: 2nd stage retry on SIGA-W busy conditions (bnc#713138,
     LTC#74402).

   - TTY: pty, fix pty counting (bnc#711203).

   - Avoid deadlock in GFP_IO/GFP_FS allocation (bnc#632870).

   - novfs: fix some DirCache locking issues (bnc#669378).
   - novfs: fix some kmalloc/kfree issues (bnc#669378).
   - novfs: fix off-by-one allocation error (bnc#669378).
   - novfs: unlink directory after unmap (bnc#649625).
   - novfs: last modification time not reliable (bnc#642896).

   - x86 / IO APIC: Reset IRR in clear_IO_APIC_pin() (bnc#701686,
     bnc#667386).

   - mptfusion : Added check for SILI bit in READ_6 CDB for DATA UNDERRUN
     ERRATA (bnc #712456).

   - xfs: serialize unaligned direct IOs (bnc#707125).

   - NFS: Ensure that we handle NFS4ERR_STALE_STATEID correctly
     (bnc#701443).
   - NFSv4: Do not call nfs4_state_mark_reclaim_reboot() from error
     handlers (bnc#701443).
   - NFSv4: Fix open recovery (bnc#701443).
   - NFSv4.1: Do not call nfs4_schedule_state_recovery() unnecessarily
     (bnc#701443)

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 High Availability Extension 11 SP1
     http://download.novell.com/patch/finder/?keywords=20cb09e23614f5f5085f698cc5bf2e4f
     http://download.novell.com/patch/finder/?keywords=94fa14c210d027059a56ea1e31e280c7
     http://download.novell.com/patch/finder/?keywords=9a7f6196af0af6d69bc4d0f12e07e44d
     http://download.novell.com/patch/finder/?keywords=959314df0926c9887f7057c56f1d07c1
     http://download.novell.com/patch/finder/?keywords=56d0712d83970cf6fe7492bf3330ee2a

   SUSE Linux Enterprise Desktop 11 SP1
     http://download.novell.com/patch/finder/?keywords=959314df0926c9887f7057c56f1d07c1
     http://download.novell.com/patch/finder/?keywords=56d0712d83970cf6fe7492bf3330ee2a

   SUSE Linux Enterprise Server 11 SP1
     http://download.novell.com/patch/finder/?keywords=20cb09e23614f5f5085f698cc5bf2e4f
     http://download.novell.com/patch/finder/?keywords=94fa14c210d027059a56ea1e31e280c7
     http://download.novell.com/patch/finder/?keywords=9a7f6196af0af6d69bc4d0f12e07e44d
     http://download.novell.com/patch/finder/?keywords=959314df0926c9887f7057c56f1d07c1
     http://download.novell.com/patch/finder/?keywords=56d0712d83970cf6fe7492bf3330ee2a

______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   none
______________________________________________________________________________

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