The ipt_recent kernel module (ipt_recent.c) in Linux kernel before 2.6.12, when running on 64-bit processors such as AMD64, allows remote attackers to cause a denial of service (kernel panic) via certain attacks such as SSH brute force, which leads to memset calls using a length based on the u_int32_t type, acting on an array of unsigned long elements, a different vulnerability than CVE-2005-2873.

Several local and remote vulnerabilities have been discovered in the Linux kernel that may lead to a denial of service or the execution of arbitrary code. The Common Vulnerabilities and Exposures project identifies the following problems :

  - CVE-2004-2302     A race condition in the sysfs filesystem allows local     users to read kernel memory and cause a denial of     service (crash).

  - CVE-2005-0756     Alexander Nyberg discovered that the ptrace() system     call does not properly verify addresses on the amd64     architecture which can be exploited by a local attacker     to crash the kernel.

  - CVE-2005-0757     A problem in the offset handling in the xattr file     system code for ext3 has been discovered that may allow     users on 64-bit systems that have access to an ext3     filesystem with extended attributes to cause the kernel     to crash.

  - CVE-2005-1265     Chris Wright discovered that the mmap() function could     create illegal memory maps that could be exploited by a     local user to crash the kernel or potentially execute     arbitrary code.

  - CVE-2005-1761     A vulnerability on the IA-64 architecture can lead local     attackers to overwrite kernel memory and crash the     kernel.

  - CVE-2005-1762     A vulnerability has been discovered in the ptrace()     system call on the amd64 architecture that allows a     local attacker to cause the kernel to crash.

  - CVE-2005-1763     A buffer overflow in the ptrace system call for 64-bit     architectures allows local users to write bytes into     arbitrary kernel memory.

  - CVE-2005-1765     Zou Nan Hai has discovered that a local user could cause     the kernel to hang on the amd64 architecture after     invoking syscall() with specially crafted arguments.

  - CVE-2005-1767     A vulnerability has been discovered in the stack segment     fault handler that could allow a local attacker to cause     a stack exception that will lead the kernel to crash     under certain circumstances.

  - CVE-2005-2456     Balazs Scheidler discovered that a local attacker could     call setsockopt() with an invalid xfrm_user policy     message which would cause the kernel to write beyond the     boundaries of an array and crash.

  - CVE-2005-2458     Vladimir Volovich discovered a bug in the zlib routines     which are also present in the Linux kernel and allows     remote attackers to crash the kernel.

  - CVE-2005-2459     Another vulnerability has been discovered in the zlib     routines which are also present in the Linux kernel and     allows remote attackers to crash the kernel.

  - CVE-2005-2548     Peter Sandstrom noticed that snmpwalk from a remote host     could cause a denial of service (kernel oops from null     dereference) via certain UDP packets that lead to a     function call with the wrong argument.

  - CVE-2005-2801     Andreas Gruenbacher discovered a bug in the ext2 and     ext3 file systems. When data areas are to be shared     among two inodes not all information were compared for     equality, which could expose wrong ACLs for files.

  - CVE-2005-2872     Chad Walstrom discovered that the ipt_recent kernel     module on 64-bit processors such as AMD64 allows remote     attackers to cause a denial of service (kernel panic)     via certain attacks such as SSH brute force.

  - CVE-2005-3105     The mprotect code on Itanium IA-64 Montecito processors     does not properly maintain cache coherency as required     by the architecture, which allows local users to cause a     denial of service and possibly corrupt data by modifying     PTE protections.

  - CVE-2005-3106     A race condition in the thread management may allow     local users to cause a denial of service (deadlock) when     threads are sharing memory and waiting for a thread that     has just performed an exec.

  - CVE-2005-3107     When one thread is tracing another thread that shares     the same memory map a local user could cause a denial of     service (deadlock) by forcing a core dump when the     traced thread is in the TASK_TRACED state.

  - CVE-2005-3108     A bug in the ioremap() system call has been discovered     on the amd64 architecture that could allow local users     to cause a denial of service or an information leak when     performing a lookup of a non-existent memory page.

  - CVE-2005-3109     The HFS and HFS+ (hfsplus) modules allow local attackers     to cause a denial of service (oops) by using hfsplus to     mount a filesystem that is not hfsplus.

  - CVE-2005-3110     A race condition in the ebtables netfilter module on an     SMP system running under high load may allow remote     attackers to cause a denial of service (crash).

  - CVE-2005-3271     Roland McGrath discovered that exec() does not properly     clear posix-timers in multi-threaded environments, which     results in a resource leak and could allow a large     number of multiple local users to cause a denial of     service by using more posix-timers than specified by the     quota for a single user.

  - CVE-2005-3272     The kernel allows remote attackers to poison the bridge     forwarding table using frames that have already been     dropped by filtering, which can cause the bridge to     forward spoofed packets.

  - CVE-2005-3273     The ioctl for the packet radio ROSE protocol does not     properly verify the arguments when setting a new router,     which allows attackers to trigger out-of-bounds errors.

  - CVE-2005-3274     A race condition on SMP systems allows local users to     cause a denial of service (null dereference) by causing     a connection timer to expire while the connection table     is being flushed before the appropriate lock is     acquired.

  - CVE-2005-3275     An error in the NAT code allows remote attackers to     cause a denial of service (memory corruption) by causing     two packets for the same protocol to be NATed at the     same time, which leads to memory corruption.

  - CVE-2005-3276     A missing memory cleanup in the thread handling routines     before copying data into userspace allows a user process     to obtain sensitive information.

This update also contains a number of corrections for issues that turned out to have no security implication afterwards.

Several local and remote vulnerabilities have been discovered in the Linux kernel that may lead to a denial of service or the execution of arbitrary code. The Common Vulnerabilities and Exposures project identifies the following problems :

  - CVE-2005-0756     Alexander Nyberg discovered that the ptrace() system     call does not properly verify addresses on the amd64     architecture which can be exploited by a local attacker     to crash the kernel.

  - CVE-2005-0757     A problem in the offset handling in the xattr file     system code for ext3 has been discovered that may allow     users on 64-bit systems that have access to an ext3     filesystem with extended attributes to cause the kernel     to crash.

  - CVE-2005-1762     A vulnerability has been discovered in the ptrace()     system call on the amd64 architecture that allows a     local attacker to cause the kernel to crash.

  - CVE-2005-1767     A vulnerability has been discovered in the stack segment     fault handler that could allow a local attacker to cause     a stack exception that will lead the kernel to crash     under certain circumstances.

  - CVE-2005-1768     Ilja van Sprundel discovered a race condition in the     IA32 (x86) compatibility execve() systemcall for amd64     and IA64 that allows local attackers to cause the kernel     to panic and possibly execute arbitrary code.

  - CVE-2005-2456     Balazs Scheidler discovered that a local attacker could     call setsockopt() with an invalid xfrm_user policy     message which would cause the kernel to write beyond the     boundaries of an array and crash.

  - CVE-2005-2458     Vladimir Volovich discovered a bug in the zlib routines     which are also present in the Linux kernel and allows     remote attackers to crash the kernel.

  - CVE-2005-2459     Another vulnerability has been discovered in the zlib     routines which are also present in the Linux kernel and     allows remote attackers to crash the kernel.

  - CVE-2005-2553     A NULL pointer dereference in ptrace when tracing a     64-bit executable can cause the kernel to crash.

  - CVE-2005-2801     Andreas Gruenbacher discovered a bug in the ext2 and     ext3 file systems. When data areas are to be shared     among two inodes not all information were compared for     equality, which could expose wrong ACLs for files.

  - CVE-2005-2872     Chad Walstrom discovered that the ipt_recent kernel     module to stop SSH bruteforce attacks could cause the     kernel to crash on 64-bit architectures.

  - CVE-2005-3275     An error in the NAT code allows remote attackers to     cause a denial of service (memory corruption) by causing     two packets for the same protocol to be NATed at the     same time, which leads to memory corruption.

Updated kernel packages are now available as part of ongoing support and maintenance of Red Hat Enterprise Linux version 4. This is the second regular update.

This update has been rated as having important security impact by the Red Hat Security Response Team.

The Linux kernel handles the basic functions of the operating system.

This is the second regular kernel update to Red Hat Enterprise Linux 4.

New features introduced in this update include: - Audit support - systemtap - kprobes, relayfs - Keyring support - iSCSI Initiator - iscsi_sfnet 4:0.1.11-1 - Device mapper multipath support - Intel dual core support - esb2 chipset support - Increased exec-shield coverage - Dirty page tracking for HA systems - Diskdump -- allow partial diskdumps and directing to swap

There were several bug fixes in various parts of the kernel. The ongoing effort to resolve these problems has resulted in a marked improvement in the reliability and scalability of Red Hat Enterprise Linux 4.

The following security bugs were fixed in this update, detailed below with corresponding CAN names available from the Common Vulnerabilities and Exposures project (cve.mitre.org) :

  - flaws in ptrace() syscall handling on 64-bit systems     that allowed a local user to cause a denial of service     (crash) (CVE-2005-0756, CVE-2005-1761, CVE-2005-1762,     CVE-2005-1763)

  - flaws in IPSEC network handling that allowed a local     user to cause a denial of service or potentially gain     privileges (CVE-2005-2456, CVE-2005-2555)

  - a flaw in sendmsg() syscall handling on 64-bit systems     that allowed a local user to cause a denial of service     or potentially gain privileges (CVE-2005-2490)

  - a flaw in sendmsg() syscall handling that allowed a     local user to cause a denial of service by altering     hardware state (CVE-2005-2492)

  - a flaw that prevented the topdown allocator from     allocating mmap areas all the way down to address zero     (CVE-2005-1265)

  - flaws dealing with keyrings that could cause a local     denial of service (CVE-2005-2098, CVE-2005-2099)

  - a flaw in the 4GB split patch that could allow a local     denial of service (CVE-2005-2100)

  - a xattr sharing bug in the ext2 and ext3 file systems     that could cause default ACLs to disappear     (CVE-2005-2801)

  - a flaw in the ipt_recent module on 64-bit architectures     which could allow a remote denial of service     (CVE-2005-2872)

The following device drivers have been upgraded to new versions :

qla2100 --------- 8.00.00b21-k to 8.01.00b5-rh2 qla2200 --------- 8.00.00b21-k to 8.01.00b5-rh2 qla2300 --------- 8.00.00b21-k to 8.01.00b5-rh2 qla2322 --------- 8.00.00b21-k to 8.01.00b5-rh2 qla2xxx
--------- 8.00.00b21-k to 8.01.00b5-rh2 qla6312 --------- 8.00.00b21-k to 8.01.00b5-rh2 megaraid_mbox --- 2.20.4.5 to 2.20.4.6 megaraid_mm
----- 2.20.2.5 to 2.20.2.6 lpfc ------------ 0:8.0.16.6_x2 to 0:8.0.16.17 cciss ----------- 2.6.4 to 2.6.6 ipw2100 --------- 1.0.3 to 1.1.0 tg3 ------------- 3.22-rh to 3.27-rh e100 ------------ 3.3.6-k2-NAPI to 3.4.8-k2-NAPI e1000 ----------- 5.6.10.1-k2-NAPI to 6.0.54-k2-NAPI 3c59x ----------- LK1.1.19 mptbase --------- 3.01.16 to 3.02.18 ixgb ------------ 1.0.66 to 1.0.95-k2-NAPI libata ---------- 1.10 to 1.11 sata_via -------- 1.0 to 1.1 sata_ahci ------- 1.00 to 1.01 sata_qstor ------ 0.04 sata_sil -------- 0.8 to 0.9 sata_svw
-------- 1.05 to 1.06 s390: crypto ---- 1.31 to 1.57 s390: zfcp ------ s390: CTC-MPC --- s390: dasd ------- s390: cio ------- s390: qeth
------

All Red Hat Enterprise Linux 4 users are advised to upgrade their kernels to the packages associated with their machine architectures and configurations as listed in this erratum.

Oleg Nesterov discovered a local Denial of Service vulnerability in the timer handling. When a non group-leader thread called exec() to execute a different program while an itimer was pending, the timer expiry would signal the old group leader task, which did not exist any more. This caused a kernel panic. This vulnerability only affects Ubuntu 5.04. (CAN-2005-1913)

Al Viro discovered that the sendmsg() function did not sufficiently validate its input data. By calling sendmsg() and at the same time modifying the passed message in another thread, he could exploit this to execute arbitrary commands with kernel privileges. This only affects the amd64 bit platform. (CAN-2005-2490)

Al Viro discovered a vulnerability in the raw_sendmsg() function. By calling this function with specially crafted arguments, a local attacker could either read kernel memory contents (leading to information disclosure) or manipulate the hardware state by reading certain IO ports. This vulnerability only affects Ubuntu 5.04.
(CAN-2005-2492)

Jan Blunck discovered a Denial of Service vulnerability in the procfs interface of the SCSI driver. By repeatedly reading /proc/scsi/sg/devices, a local attacker could eventually exhaust kernel memory. (CAN-2005-2800)

A flaw was discovered in the handling of extended attributes on ext2 and ext3 file systems. Under certain condidions, this could prevent the enforcement of Access Control Lists, which eventually could lead to information disclosure, unauthorized program execution, or unauthorized data modification. This does not affect the standard Unix permissions. (CAN-2005-2801)

Chad Walstrom discovered a Denial of Service in the ipt_recent module, which can be used in netfilter (Firewall configuration). A remote attacker could exploit this to crash the kernel by sending certain packets (such as an SSH brute-force attack) to a host which uses the 'recent' module. (CAN-2005-2802).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

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

An integer overflow in vc_resize (CVE-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 (CVE-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).

A DoS in pkt_ioctl in pktcdvc.c (CVE-2005-1589).

An array index overflow in the xfrm_sk_policy_insert function in xfrm_user.c allows local users to cause a DoS (oops or deadlock) and possibly execute arbitrary code (CVE-2005-2456).

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

inflate.c in the zlib routines in versions prior to 2.6.12.5 allow remove attackers to cause a DoS (crash) via a compressed file with 'improper tables' (CVE-2005-2458).

The huft_build function in inflate.c in the zlib routines in versions prior to 2.6.12.5 returns the wrong value, allowing remote attackers to cause a DoS (crash) via a certain compressed file that leads to a NULL pointer dereference (CVE-2005-2459).

A stack-based buffer overflow in the sendmsg function call in versions prior to 2.6.13.1 allow local users to execute arbitrary code by calling sendmsg and modifying the message contents in another thread (CVE-2005-2490).

vlan_dev.c in version 2.6.8 allows remote attackers to cause a DoS (oops from null dereference) via certain UDP packets that lead to a function call with the wrong argument (CVE-2005-2548).

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

xattr.c in the ext2 and ext3 file system code does not properly compare the name_index fields when sharing xattr blocks which could prevent ACLs from being applied (CVE-2005-2801).

The ipt_recent module in versions prior to 2.6.12 when running on 64bit processors allows remote attackers to cause a DoS (kernel panic) via certain attacks such as SSH brute force (CVE-2005-2872).

The ipt_recent module in versions prior to 2.6.12 does not properly perform certain tests when the jiffies value is greater than LONG_MAX, which can cause ipt_recent netfilter rules to block too early (CVE-2005-2873).

Multiple vulnerabilities in versions prior to 2.6.13.2 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).

The sys_set_mempolicy function in mempolicy.c allows local users to cause a DoS via a negative first argument (CVE-2005-3053).

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 (CVE-2005-3181).

The VT implementation in version 2.6.12 allows local users to use certain IOCTLs on terminals of other users and gain privileges (CVE-2005-3257).

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 2.6.12.4 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 :

Driver updates were made to the aic97xx and sata_sil modules.

Support was added for ATI ipx400 chipsets, for IDE and sound.

A build problem with icecream on the x86_64 platform was fixed.

The pin1 APIC timer on RS480-based motherboards was disabled.

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 :

http://www.mandriva.com/en/security/kernelupdate

The remote Redhat Enterprise Linux 4 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2005:514 advisory.

    The Linux kernel handles the basic functions of the operating system.

    This is the second regular kernel update to Red Hat Enterprise Linux 4.

    New features introduced in this update include:
    - Audit support
    - systemtap - kprobes, relayfs
    - Keyring support
    - iSCSI Initiator - iscsi_sfnet 4:0.1.11-1
    - Device mapper multipath support
    - Intel dual core support
    - esb2 chipset support
    - Increased exec-shield coverage
    - Dirty page tracking for HA systems
    - Diskdump -- allow partial diskdumps and directing to swap

    There were several bug fixes in various parts of the kernel. The ongoing     effort to resolve these problems has resulted in a marked improvement     in the reliability and scalability of Red Hat Enterprise Linux 4.

    The following security bugs were fixed in this update, detailed below with     corresponding CAN names available from the Common Vulnerabilities and     Exposures project (cve.mitre.org):

    - flaws in ptrace() syscall handling on 64-bit systems that allowed a local     user to cause a denial of service (crash) (CAN-2005-0756, CAN-2005-1761,     CAN-2005-1762, CAN-2005-1763)

    - flaws in IPSEC network handling that allowed a local user to cause a     denial of service or potentially gain privileges (CAN-2005-2456, CAN-2005-2555)

    - a flaw in sendmsg() syscall handling on 64-bit systems that allowed a     local user to cause a denial of service or potentially gain privileges     (CAN-2005-2490)

    - a flaw in sendmsg() syscall handling that allowed a local user to cause a     denial of service by altering hardware state (CAN-2005-2492)

    - a flaw that prevented the topdown allocator from allocating mmap areas     all the way down to address zero (CAN-2005-1265)

    - flaws dealing with keyrings that could cause a local denial of service     (CAN-2005-2098, CAN-2005-2099)

    - a flaw in the 4GB split patch that could allow a local denial of service     (CAN-2005-2100)

    - a xattr sharing bug in the ext2 and ext3 file systems that could cause     default ACLs to disappear (CAN-2005-2801)

    - a flaw in the ipt_recent module on 64-bit architectures which could allow     a remote denial of service (CAN-2005-2872)

    The following device drivers have been upgraded to new versions:

    qla2100 --------- 8.00.00b21-k to 8.01.00b5-rh2     qla2200 --------- 8.00.00b21-k to 8.01.00b5-rh2     qla2300 --------- 8.00.00b21-k to 8.01.00b5-rh2     qla2322 --------- 8.00.00b21-k to 8.01.00b5-rh2     qla2xxx --------- 8.00.00b21-k to 8.01.00b5-rh2     qla6312 --------- 8.00.00b21-k to 8.01.00b5-rh2     megaraid_mbox --- 2.20.4.5 to 2.20.4.6     megaraid_mm ----- 2.20.2.5 to 2.20.2.6     lpfc ------------ 0:8.0.16.6_x2 to 0:8.0.16.17     cciss ----------- 2.6.4 to 2.6.6     ipw2100 --------- 1.0.3 to 1.1.0     tg3 ------------- 3.22-rh to 3.27-rh     e100 ------------ 3.3.6-k2-NAPI to 3.4.8-k2-NAPI     e1000 ----------- 5.6.10.1-k2-NAPI to 6.0.54-k2-NAPI     3c59x ----------- LK1.1.19     mptbase --------- 3.01.16 to 3.02.18     ixgb ------------ 1.0.66 to 1.0.95-k2-NAPI     libata ---------- 1.10 to 1.11     sata_via -------- 1.0 to 1.1     sata_ahci ------- 1.00 to 1.01     sata_qstor ------ 0.04     sata_sil -------- 0.8 to 0.9     sata_svw -------- 1.05 to 1.06     s390: crypto ---- 1.31 to 1.57     s390: zfcp ------     s390: CTC-MPC ---     s390: dasd -------     s390: cio -------     s390: qeth ------

    All Red Hat Enterprise Linux 4 users are advised to upgrade their     kernels to the packages associated with their machine architectures     and configurations as listed in this erratum.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote CentOS system is missing a security update which has been documented in Red Hat advisory RHSA-2005-514.

ID	Name	Product	Family	Severity
22788	Debian DSA-922-1 : kernel-source-2.6.8 - several vulnerabilities	Nessus	Debian Local Security Checks	high
22787	Debian DSA-921-1 : kernel-source-2.4.27 - several vulnerabilities	Nessus	Debian Local Security Checks	medium
21943	CentOS 4 : kernel (CESA-2005:514)	Nessus	CentOS Local Security Checks	high
20588	Ubuntu 4.10 / 5.04 : linux-source-2.6.10, linux-source-2.6.8.1 vulnerabilities (USN-178-1)	Nessus	Ubuntu Local Security Checks	medium
20450	Mandrake Linux Security Advisory : kernel (MDKSA-2005:219)	Nessus	Mandriva Local Security Checks	high
19989	RHEL 4 : Updated kernel packages available for Red Hat Enterprise Linux 4 Update 2 (Important) (RHSA-2005:514)	Nessus	Red Hat Local Security Checks	high
801409	CentOS RHSA-2005-514 Security Check	Log Correlation Engine	Generic	high

Detections

Analytics

CVE-2005-2872

high

Tenable Plugins

high

medium

high

medium

high

high

high