<?xml version="1.0" encoding="UTF-8"?>
<!--PATCHINFO id="ae34197f7a01df2900bcf50d77b9b261"!-->
<patch
    xmlns="http://novell.com/package/metadata/suse/patch"
    xmlns:yum="http://linux.duke.edu/metadata/common"
    xmlns:rpm="http://linux.duke.edu/metadata/rpm"
    xmlns:suse="http://novell.com/package/metadata/suse/common"
    patchid="slesp2-kernel-6236"
    timestamp="1242133098"
    engine="1.0">
  <yum:name>slesp2-kernel</yum:name>
  <summary lang="en">Security update for the Linux kernel</summary>
  <summary lang="de">Security update for the Linux kernel</summary>
  <description lang="en">The Linux kernel on SUSE Linux Enterprise 10 Service Pack 2
was updated to fix various security issues and several bugs.

Following security issues were fixed: 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 &quot;cifs&quot;
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).

The GCC option -fwrapv has been added to compilation to
work around potentially removing integer overflow checks.

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 &quot;garbage&quot; memory to be sent.

Also a number of bugs were fixed, for details please see
the RPM changelog.
</description>
  <description lang="de">The Linux kernel on SUSE Linux Enterprise 10 Service Pack 2
was updated to fix various security issues and several bugs.

Following security issues were fixed: 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 &quot;cifs&quot;
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).

The GCC option -fwrapv has been added to compilation to
work around potentially removing integer overflow checks.

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 &quot;garbage&quot; memory to be sent.

Also a number of bugs were fixed, for details please see
the RPM changelog.
</description>
  <yum:version ver="6236" rel="0"/>
  <rpm:requires>
    <rpm:entry kind="atom" name="kernel-debug" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="EQ"/>
    <rpm:entry kind="atom" name="kernel-default" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="EQ"/>
    <rpm:entry kind="atom" name="kernel-kdump" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="EQ"/>
    <rpm:entry kind="atom" name="kernel-smp" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="EQ"/>
    <rpm:entry kind="atom" name="kernel-source" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="EQ"/>
    <rpm:entry kind="atom" name="kernel-syms" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="EQ"/>
    <rpm:entry kind="atom" name="kernel-xen" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="EQ"/>
  </rpm:requires>
  <reboot-needed/>
  <category>security</category>
    <license-to-confirm>
This update can be used to install a new kernel.
 
If you decide to use the kernel update, we recommend that you reboot
your system upon completion of the YaST Online Update, as additional
kernel modules may be needed which can only be loaded after the system
is rebooted.

If you are in the course of performing a new installation, the installer
will reboot the machine after installing the patch. If you do not want 
to reboot, deselect this patch.
    </license-to-confirm>
  <atoms>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>kernel-debug</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="2.6.16.60" rel="0.39.3"/>
      <checksum type="sha" pkgid="YES">faee3b8c073ebc03bd155367c5a09b70991e2966</checksum>
      <time file="1242144132" build="1242133098"/>
      <size package="19088568" installed="85914023" archive="82786836"/>
      <location xml:base="media://#1" href="suse/x86_64/kernel-debug-2.6.16.60-0.42.5.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="kernel-debug" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="kernel-debug"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>kernel-default</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="2.6.16.60" rel="0.39.3"/>
      <checksum type="sha" pkgid="YES">cf4c5701d0fe13fe097aefd32a1ee67fbb298f0c</checksum>
      <time file="1242144084" build="1242132631"/>
      <size package="17923837" installed="58607346" archive="55474636"/>
      <location xml:base="media://#1" href="suse/x86_64/kernel-default-2.6.16.60-0.42.5.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="kernel-default" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="kernel-default"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>kernel-kdump</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="2.6.16.60" rel="0.39.3"/>
      <checksum type="sha" pkgid="YES">3ef047b477c68dddff5f8799acd9183f5f5007d8</checksum>
      <time file="1242144100" build="1242132125"/>
      <size package="16496182" installed="61722476" archive="58594664"/>
      <location xml:base="media://#1" href="suse/x86_64/kernel-kdump-2.6.16.60-0.42.5.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="kernel-kdump" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="kernel-kdump"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>kernel-smp</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="2.6.16.60" rel="0.39.3"/>
      <checksum type="sha" pkgid="YES">fd26f4ac169abf3c0585f748aba93fec01a7795f</checksum>
      <time file="1242144116" build="1242133419"/>
      <size package="18333653" installed="84189738" archive="81066624"/>
      <location xml:base="media://#1" href="suse/x86_64/kernel-smp-2.6.16.60-0.42.5.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="kernel-smp" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="kernel-smp"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>kernel-source</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="2.6.16.60" rel="0.39.3"/>
      <checksum type="sha" pkgid="YES">9da9ac693f906548b1ef5e2ff23c793ba0d92c2b</checksum>
      <time file="1242144065" build="1242131058"/>
      <size package="47363548" installed="238930791" archive="242772052"/>
      <location xml:base="media://#1" href="suse/x86_64/kernel-source-2.6.16.60-0.42.5.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="kernel-source" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="kernel-source"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>kernel-syms</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="2.6.16.60" rel="0.39.3"/>
      <checksum type="sha" pkgid="YES">21f38212820a82ce15af3fa0a920356c7055f8e9</checksum>
      <time file="1242144148" build="1242133831"/>
      <size package="1929344" installed="2059205" archive="2062124"/>
      <location xml:base="media://#1" href="suse/x86_64/kernel-syms-2.6.16.60-0.42.5.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="kernel-syms" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="kernel-syms"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>kernel-xen</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="2.6.16.60" rel="0.39.3"/>
      <checksum type="sha" pkgid="YES">187ca9d438ddb57fb6e3a8a97af16adc7419274a</checksum>
      <time file="1242144068" build="1242132447"/>
      <size package="18224165" installed="65986666" archive="62843352"/>
      <location xml:base="media://#1" href="suse/x86_64/kernel-xen-2.6.16.60-0.42.5.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="kernel-xen" epoch="0" ver="2.6.16.60" rel="0.39.3" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="kernel-xen"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
  </atoms>
</patch>
