-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: kernel Announcement ID: SUSE-SA:2009:031 Date: Mon, 09 Jun 2009 09:00:00 +0000 Affected Products: openSUSE 11.0 Vulnerability Type: remote code execution Severity (1-10): 9 SUSE Default Package: yes Cross-References: CVE-2009-0028, CVE-2009-0065, CVE-2009-0269 CVE-2009-0322, CVE-2009-0675, CVE-2009-0676 CVE-2009-0834, CVE-2009-0835, CVE-2009-0859 CVE-2009-1072, CVE-2009-1242, CVE-2009-1265 CVE-2009-1337, CVE-2009-1439, CVE-2009-1630 CVE-2009-1961 Content of This Advisory: 1) Security Vulnerability Resolved: Linux kernel security problem 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 openSUSE 11.0 fixes some bugs and several security problems. The following security issues are fixed: CVE-2009-0065: Buffer overflow in net/sctp/sm_statefuns.c in the Stream Control Transmission Protocol (sctp) implementation in the Linux kernel allows remote attackers to remotely execute code via an FWD-TSN (aka FORWARD-TSN) chunk with a large stream ID. CVE-2009-1961: A local denial of service problem in the splice(2) system call. CVE-2009-1630: The nfs_permission function in fs/nfs/dir.c in the NFS client implementation in the Linux kernel when atomic_open is available, does not check execute (aka EXEC or MAY_EXEC) permission bits, which allows local users to bypass permissions and execute files, as demonstrated by files on an NFSv4 file server. CVE-2009-0834: The audit_syscall_entry function in the Linux kernel on the x86_64 platform did not properly handle (1) a 32-bit process making a 64-bit syscall or (2) a 64-bit process making a 32-bit syscall, which allows local users to bypass certain syscall audit configurations via crafted syscalls. CVE-2009-1072: nfsd in the Linux kernel did not drop the CAP_MKNOD capability before handling a user request in a thread, which allows local users to create device nodes, as demonstrated on a filesystem that has been exported with the root_squash option. CVE-2009-0835 The __secure_computing function in kernel/seccomp.c in the seccomp subsystem in the Linux kernel on the x86_64 platform, when CONFIG_SECCOMP is enabled, does not properly handle (1) a 32-bit process making a 64-bit syscall or (2) a 64-bit process making a 32-bit syscall, which allows local users to bypass intended access restrictions via crafted syscalls that are misinterpreted as (a) stat or (b) chmod. CVE-2009-1439: Buffer overflow in fs/cifs/connect.c in CIFS in the Linux kernel 2.6.29 and earlier allows remote attackers to cause a denial of service (crash) or potential code execution via a long nativeFileSystem field in a Tree Connect response to an SMB mount request. This requires that kernel can be made to mount a "cifs" filesystem from a malicious CIFS server. CVE-2009-1337: The exit_notify function in kernel/exit.c in the Linux kernel did not restrict exit signals when the CAP_KILL capability is held, which allows local users to send an arbitrary signal to a process by running a program that modifies the exit_signal field and then uses an exec system call to launch a setuid application. CVE-2009-0859: The shm_get_stat function in ipc/shm.c in the shm subsystem in the Linux kernel, when CONFIG_SHMEM is disabled, misinterprets the data type of an inode, which allows local users to cause a denial of service (system hang) via an SHM_INFO shmctl call, as demonstrated by running the ipcs program. (SUSE is enabling CONFIG_SHMEM, so is by default not affected, the fix is just for completeness). CVE-2009-1242: The vmx_set_msr function in arch/x86/kvm/vmx.c in the VMX implementation in the KVM subsystem in the Linux kernel on the i386 platform allows guest OS users to cause a denial of service (OOPS) by setting the EFER_LME (aka "Long mode enable") bit in the Extended Feature Enable Register (EFER) model-specific register, which is specific to the x86_64 platform. CVE-2009-1265: Integer overflow in rose_sendmsg (sys/net/af_rose.c) in the Linux kernel might allow attackers to obtain sensitive information via a large length value, which causes "garbage" memory to be sent. CVE-2009-0028: The clone system call in the Linux kernel allows local users to send arbitrary signals to a parent process from an unprivileged child process by launching an additional child process with the CLONE_PARENT flag, and then letting this new process exit. CVE-2009-0675: The skfp_ioctl function in drivers/net/skfp/skfddi.c in the Linux kernel permits SKFP_CLR_STATS requests only when the CAP_NET_ADMIN capability is absent, instead of when this capability is present, which allows local users to reset the driver statistics, related to an "inverted logic" issue. CVE-2009-0676: The sock_getsockopt function in net/core/sock.c in the Linux kernel does not initialize a certain structure member, which allows local users to obtain potentially sensitive information from kernel memory via an SO_BSDCOMPAT getsockopt request. CVE-2009-0322: drivers/firmware/dell_rbu.c in the Linux kernel allows local users to cause a denial of service (system crash) via a read system call that specifies zero bytes from the (1) image_type or (2) packet_size file in /sys/devices/platform/dell_rbu/. CVE-2009-0269: fs/ecryptfs/inode.c in the eCryptfs subsystem in the Linux kernel allows local users to cause a denial of service (fault or memory corruption), or possibly have unspecified other impact, via a readlink call that results in an error, leading to use of a -1 return value as an array index. Some other non-security bugs were fixed, please see the RPM changelog. 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 -Fhvto apply the update, replacing with the filename of the downloaded RPM package. x86 Platform: openSUSE 11.0: http://download.opensuse.org/update/11.0/rpm/i586/kernel-debug-2.6.25.20-0.4.i586.rpm http://download.opensuse.org/update/11.0/rpm/i586/kernel-default-2.6.25.20-0.4.i586.rpm http://download.opensuse.org/update/11.0/rpm/i586/kernel-pae-2.6.25.20-0.4.i586.rpm http://download.opensuse.org/update/11.0/rpm/i586/kernel-source-2.6.25.20-0.4.i586.rpm http://download.opensuse.org/update/11.0/rpm/i586/kernel-syms-2.6.25.20-0.4.i586.rpm http://download.opensuse.org/update/11.0/rpm/i586/kernel-vanilla-2.6.25.20-0.4.i586.rpm http://download.opensuse.org/update/11.0/rpm/i586/kernel-xen-2.6.25.20-0.4.i586.rpm Platform Independent: openSUSE 11.0: http://download.opensuse.org/update/11.0/rpm/noarch/kernel-docs-2.6.25.20-0.4.noarch.rpm Power PC Platform: openSUSE 11.0: http://download.opensuse.org/update/11.0/rpm/ppc/kernel-default-2.6.25.20-0.4.ppc.rpm http://download.opensuse.org/update/11.0/rpm/ppc/kernel-kdump-2.6.25.20-0.4.ppc.rpm http://download.opensuse.org/update/11.0/rpm/ppc/kernel-ppc64-2.6.25.20-0.4.ppc.rpm http://download.opensuse.org/update/11.0/rpm/ppc/kernel-ps3-2.6.25.20-0.4.ppc.rpm http://download.opensuse.org/update/11.0/rpm/ppc/kernel-source-2.6.25.20-0.4.ppc.rpm http://download.opensuse.org/update/11.0/rpm/ppc/kernel-syms-2.6.25.20-0.4.ppc.rpm http://download.opensuse.org/update/11.0/rpm/ppc/kernel-vanilla-2.6.25.20-0.4.ppc.rpm x86-64 Platform: openSUSE 11.0: http://download.opensuse.org/update/11.0/rpm/x86_64/kernel-debug-2.6.25.20-0.4.x86_64.rpm http://download.opensuse.org/update/11.0/rpm/x86_64/kernel-default-2.6.25.20-0.4.x86_64.rpm http://download.opensuse.org/update/11.0/rpm/x86_64/kernel-source-2.6.25.20-0.4.x86_64.rpm http://download.opensuse.org/update/11.0/rpm/x86_64/kernel-syms-2.6.25.20-0.4.x86_64.rpm http://download.opensuse.org/update/11.0/rpm/x86_64/kernel-vanilla-2.6.25.20-0.4.x86_64.rpm http://download.opensuse.org/update/11.0/rpm/x86_64/kernel-xen-2.6.25.20-0.4.x86_64.rpm Sources: openSUSE 11.0: ______________________________________________________________________________ 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. ====================================================================