Home > Security > Advisories


Mandriva Advisories

Package name kernel
Date November 30th, 2005
Advisory ID MDKSA-2005:218
Affected versions CS3.0, MNF2.0
Synopsis Updated kernel packages fix numerous vulnerabilities

Problem Description

Multiple vulnerabilities in the Linux 2.6 kernel have been discovered
and corrected in this update:

An integer overflow in vc_resize (CAN-2004-1333).

A race condition in the sysfs_read_file and sysfs_write_file functions
in 2.6.10 and earlier allows local users to read kernel memory and
cause a DoS (crash) via large offsets in sysfs files (CAN-2004-2302).

An integer signedness error in scsi_ioctl.c (CVE-2005-0180).

Netfilter allows a local user to cause a DoS (memory consumption) via
certain packet fragments that are reassembled twice, which causes a
data structure to be allocated twice (CVE-2005-0210).

The netfilter/iptables module in versions prior to allow remote
attackers to cause a DoS (crash) or bypass firewall rules via crafted
packets, which are not properly handled by skb_checksum_help function

The zisofs driver in versions prior to allows local users and
remove attackers to cause a DoS (crash) via a crafted compressed ISO
filesystem (CVE-2005-2457).

The kernel does not properly restrict socket policy access to users
with the CAP_NET_ADMIN capability, which could allow local users to
conduct unauthorized activities via ipv4/ip_sockglue.c and
ipv6/ipv6_sockglue.c (CVE-2005-2555).

A memory leak in the seq_file implementation in the SCSI procfs
interface (sg.c) in 2.6.13 and earlier allows a local user to cause a
DoS (memory consumption) via certain repeated reads from
/proc/scsi/gs/devices file which is not properly handled when the
next() interator returns NULL or an error (CVE-2005-2800).

Multiple vulnerabilities in versions prior to allow local
users to cause a DoS (oops from null dereference) via fput in a 32bit
ioctl on 64-bit x86 systems or sockfd_put in the 32-bit routing_ioctl
function on 64-bit systems (CVE-2005-3044).

Versions 2.6.8 to 2.6.14-rc2 allow local users to cause a DoS (oops)
via a userspace process that issues a USB Request Block (URB) to a USB
device and terminates before the URB is finished, which leads to a
stale pointer reference (CVE-2005-3055).

The Orinoco driver in 2.6.13 and earlier does not properly clear memory
from a previously used packet whose length is increased, allowing
remote attackers to obtain sensitive information (CVE-2005-3180).

Kernels 2.6.13 and earlier, when CONFIG_AUDITSYSCALL is enabled, use an
incorrect function to free names_cache memory, preventing the memory
from being tracked by AUDITSYSCALL code and leading to a memory leak

The VT implementation in version 2.6.12 allows local users to use
certain IOCTLs on terminals of other users and gain privileges

Exec does not properly clear posix-timers in multi-threaded
environments, which result in a resource leak and could allow a large
number of multiple local users to cause a DoS by using more posix-
timers than specified by the quota for a single user (CVE-2005-3271).

The rose_rt_ioctl function rose_route.c in versions prior to 2.6.12
does not properly verify the ndigis argument for a new route, allowing
an attacker to trigger array out-of-bounds errors with a large number
of digipeats (CVE-2005-3273).

A race condition in ip_vs_conn_flush in versions prior to 2.6.13, when
running on SMP systems, allows local users to cause a DoS (null
dereference) by causing a connection timer to expire while the
connection table is being flushed before the appropriate lock is
acquired (CVE-2005-3274).

The NAT code in versions prior to 2.6.13 incorrectly declares a
variable to be static, allowing remote attackers to cause a DoS (memory
corruption) by causing two packets for the same protocol to be NATed at
the same time (CVE-2005-3275).

The sys_get_thread_area function in process.c in versions prior to and 2.6.13 does not clear a data structure before copying it
to userspace, which may allow a user process to obtain sensitive
information (CVE-2005-3276).

The following non-security fixes are also applied:

Support for the arp_ignore and arp_announce sysctls were added to the
Corporate 3 kernels (bugzilla #16346).

The provided packages are patched to fix these vulnerabilities. All
users are encouraged to upgrade to these updated kernels.

To update your kernel, please follow the directions located at:


Updated Packages

Corporate Server 3.0

 7e38bcdc8a3900485d17d08e13963700  corporate/3.0/RPMS/kernel-
 be4dc943991be67f9f612ac5ca2f6c10  corporate/3.0/RPMS/kernel-enterprise-
 9acc6e90b1a8620be6af552baa8524ab  corporate/3.0/RPMS/kernel-i686-up-4GB-
 1a171d91312764089f2f0c84a6e9131a  corporate/3.0/RPMS/kernel-p3-smp-64GB-
 e6f42b56669ca4ac5515d728051c4f88  corporate/3.0/RPMS/kernel-secure-
 5f3e473fae7614433328756156f2b953  corporate/3.0/RPMS/kernel-smp-
 c98b0f07cb49a918201d2daa1ac23e7c  corporate/3.0/RPMS/kernel-source-2.6.3-29mdk.i586.rpm
 e816bcde98728e85a86c565259364f8a  corporate/3.0/RPMS/kernel-source-stripped-2.6.3-29mdk.i586.rpm
 b2497e007272f38b30e98b4231a77a76  corporate/3.0/SRPMS/kernel-

Corporate Server 3.0/X86_64

 5261e06d1085ff9c61bf29789f10669f  x86_64/corporate/3.0/RPMS/kernel-
 3cb631841cf4e9d29e1f667d940d9ab4  x86_64/corporate/3.0/RPMS/kernel-secure-
 61024ad1c23dbde624c3cd43c8805f26  x86_64/corporate/3.0/RPMS/kernel-smp-
 ba1514dcafcc748796bd9b23cd1905e4  x86_64/corporate/3.0/RPMS/kernel-source-2.6.3-29mdk.x86_64.rpm
 48a9eb1de36653665e6d7de333d25cb0  x86_64/corporate/3.0/RPMS/kernel-source-stripped-2.6.3-29mdk.x86_64.rpm
 b2497e007272f38b30e98b4231a77a76  x86_64/corporate/3.0/SRPMS/kernel-

Multi Network Firewall 2.0

 7e38bcdc8a3900485d17d08e13963700  mnf/2.0/RPMS/kernel-
 9acc6e90b1a8620be6af552baa8524ab  mnf/2.0/RPMS/kernel-i686-up-4GB-
 1a171d91312764089f2f0c84a6e9131a  mnf/2.0/RPMS/kernel-p3-smp-64GB-
 e6f42b56669ca4ac5515d728051c4f88  mnf/2.0/RPMS/kernel-secure-
 5f3e473fae7614433328756156f2b953  mnf/2.0/RPMS/kernel-smp-
 b2497e007272f38b30e98b4231a77a76  mnf/2.0/SRPMS/kernel-




To upgrade your kernel, view the kernel update instructions. Kernels cannot be upgraded via MandrivaUpdate.


Please verify the update prior to upgrading to ensure the integrity of the downloaded package. You can do this with the command :

                rpm --checksig package.rpm

You can get the GPG public key of the Mandriva Security Team to verify the GPG signature of each RPM.