Integer signedness error in the cpufreq proc handler (cpufreq_procctl) in Linux kernel 2.6 allows local users to gain privileges.

The remote host is affected by the vulnerability described in GLSA-200407-02 (Linux Kernel: Multiple vulnerabilities)

    Multiple flaws have been discovered in the Linux kernel. This advisory     corrects the following issues:
    CAN-2004-0109: This vulnerability allows privilege escalation using     ISO9660 file systems through a buffer overflow via a malformed file     system containing a long symbolic link entry. This can allow arbitrary     code execution at kernel level.
    CAN-2004-0133: The XFS file system in 2.4 series kernels has an     information leak by which data in the memory can be written to the     device hosting the file system, allowing users to obtain portions of     kernel memory by reading the raw block device.
    CAN-2004-0177: The ext3 file system in 2.4 series kernels does not     properly initialize journal descriptor blocks, causing an information     leak by which data in the memory can be written to the device hosting     the file system, allowing users to obtain portions of kernel memory by     reading the raw device.
    CAN-2004-0181: The JFS file system in 2.4 series kernels has an     information leak by which data in the memory can be written to the     device hosting the file system, allowing users to obtain portions of     kernel memory by reading the raw device.
    CAN-2004-0178: The OSS Sound Blaster [R] Driver has a Denial of Service     vulnerability since it does not handle certain sample sizes properly.
    This allows local users to hang the kernel.
    CAN-2004-0228: Due to an integer signedness error in the CPUFreq /proc     handler code in 2.6 series Linux kernels, local users can escalate     their privileges.
    CAN-2004-0229: The framebuffer driver in 2.6 series kernel drivers does     not use the fb_copy_cmap method of copying structures. The impact of     this issue is unknown, however.
    CAN-2004-0394: A buffer overflow in the panic() function of 2.4 series     Linux kernels exists, but it may not be exploitable under normal     circumstances due to its functionality.
    CAN-2004-0427: The do_fork() function in both 2.4 and 2.6 series Linux     kernels does not properly decrement the mm_count counter when an error     occurs, triggering a memory leak that allows local users to cause a     Denial of Service by exhausting other applications of memory; causing     the kernel to panic or to kill services.
    CAN-2004-0495: Multiple vulnerabilities found by the Sparse source     checker in the kernel allow local users to escalate their privileges or     gain access to kernel memory.
    CAN-2004-0535: The e1000 NIC driver does not properly initialize memory     structures before using them, allowing users to read kernel memory.
    CAN-2004-0554: 2.4 and 2.6 series kernels running on an x86 or an AMD64     architecture allow local users to cause a Denial of Service by a total     system hang, due to an infinite loop that triggers a signal handler     with a certain sequence of fsave and frstor instructions.
    Local DoS in PaX: If ASLR is enabled as a GRSecurity PaX feature, a     Denial of Service can be achieved by putting the kernel into an     infinite loop. Only 2.6 series GRSecurity kernels are affected by this     issue.
    RSBAC 1.2.3 JAIL issues: A flaw in the RSBAC JAIL implementation allows     suid/sgid files to be created inside the jail since the relevant module     does not check the corresponding mode values. This can allow privilege     escalation inside the jail. Only rsbac-(dev-)sources are affected by     this issue.
  Impact :

    Arbitrary code with normal non-super-user privileges may be able to     exploit any of these vulnerabilities; gaining kernel level access to     memory structures and hardware devices. This may be used for further     exploitation of the system, to leak sensitive data or to cause a Denial     of Service on the affected kernel.
  Workaround :

    Although users may not be affected by certain vulnerabilities, all     kernels are affected by the CAN-2004-0394, CAN-2004-0427 and     CAN-2004-0554 issues which have no workaround. As a result, all users     are urged to upgrade their kernels to patched versions.

Brad Spender discovered an exploitable bug in the cpufreq code in the Linux 2.6 kernel (CVE-2004-0228).

As well, a permissions problem existed on some SCSI drivers; a fix from Olaf Kirch is provided that changes the mode from 0777 to 0600.

This update also provides a 10.0/amd64 kernel with fixes for the previous MDKSA-2004:037 advisory as well as the above-noted fixes.

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.mandrakesoft.com/security/kernelupdate

The remote host is missing the patch for the advisory SuSE-SA:2004:010 (Linux Kernel).


Various vulnerabilities have been fixed in the newly available kernel updates. The updates consist of fixes for the following vulnerabilities:

- The do_fork() memory leak, which could lead to a local DoS attack.
All kernels except for SLES7 are affected.
- The setsockopt() MCAST buffer overflow which allows local attackers to execute arbitrary code with root privileges. Only SLES8 based products and SL 8.1 and SL 9.0 kernels are affected by this bug.
- The misuse of the fb_copy_cmap() function which could also allow local attackers to execute arbitrary code with root privileges.
Only the SL 9.1 kernel is affected.
- The integer overflow in the cpufreq_procctl() function.
Only the SL 9.1 kernel is affected.
- The wrong permissions on /proc/scsi/qla2300/HbaApiNode which allow local attackers to start DoS attacks. SLES8 kernels and SL 8.1 and 9.0 kernels are affected.
- A buffer overflow in panic(). Although there seems no way to trigger this bug, it has been fixed.

If you use a maintained product or SuSE Linux 8.1 or 9.0, we recommend an update. If you offer shell access to users we recommend an update in any case.

A memory leak was fixed in an error path in the do_fork() routine.
This was unlikely to have caused problems in real world situations.

The information leak fixed in the previous errata was also found to affect XFS and JFS. The Common Vulnerabilities and Exposures project (cve.mitre.org) assigned the names CVE-2004-0133 and CVE-2004-0181 respectively.

A vulnerability in the OSS code for SoundBlaster 16 devices was discovered by Andreas Kies. It is possible for local users with access to the sound system to crash the machine (CVE-2004-0178).

An automated checked from http://www.coverity.com highlighted a range checking bug in the i810 DRM driver. This was fixed by Andrea Arcangeli and Chris Wright.

Arjan van de Ven discovered the framebuffer code was doing direct userspace accesses instead of using correct interfaces to write to userspace.

Brad Spengler found a signedness issue in the cpufreq proc handler which could lead to users being able to read arbitary regions of kernel memory. This was fixed by Dominik Brodowski.

Shaun Colley found a potential buffer overrun in the panic() function.
As this function does not ever return, it is unlikely that this is exploitable, but has been fixed nonetheless. The Common Vulnerabilities and Exposures project (cve.mitre.org) assigned the name CVE-2004-0394 to this issue.

Paul Starzetz and Wojciech Purczynski found a lack of bounds checking in the MCAST_MSFILTER socket option which allows user code to write into kernel space, potentially giving the attacker full root priveledges. There has already been proof of concept code published exploiting this hole in a local denial-of-service manner.
http://www.isec.pl/vulnerabilities/isec-0015-msfilter.txt has more information. The Common Vulnerabilities and Exposures project (cve.mitre.org) assigned the name CVE-2004-0424 to this issue.

The previous security errata actually missed fixes for several important problems. This has been corrected in this update.

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

ID	Name	Product	Family	Severity
14535	GLSA-200407-02 : Linux Kernel: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	high
14149	Mandrake Linux Security Advisory : kernel (MDKSA-2004:050)	Nessus	Mandriva Local Security Checks	high
13828	SuSE-SA:2004:010: Linux Kernel	Nessus	SuSE Local Security Checks	high
13692	Fedora Core 1 : kernel-2.4.22-1.2188.nptl (2004-111)	Nessus	Fedora Local Security Checks	high

Detections

Analytics

CVE-2004-0228

high

Tenable Plugins

high

high

high

high