Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Sign up!
EnGarde Community
What is the most important Linux security technology?
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Latest Newsletters
Linux Security Week: March 30th, 2015
Linux Advisory Watch: March 27th, 2015
LinuxSecurity Newsletters
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

FreeBSD: kernel Improper memory access vulnerability Print E-mail
User Rating:      How can I rate this item?
Posted by Team   
FreeBSD It may be possible for a local attacker to read and/or overwrite portions of kernel memory, resulting in disclosure of sensitive information or potential privilege escalation.

FreeBSD-SA-04:13.linux                                      Security Advisory
                                                          The FreeBSD Project

Topic:          Linux binary compatibility mode input validation error

Category:       core
Module:         kernel
Announced:      2004-06-30
Credits:        Tim Robbins
Affects:        All 4.x and 5.x releases
Corrected:      2004-06-30 17:31:44 UTC (RELENG_4)
                2004-06-30 17:34:38 UTC (RELENG_5_2, 5.2.1-RELEASE-p9)
                2004-06-30 17:33:59 UTC (RELENG_4_10, 4.10-RELEASE-p2)
                2004-06-30 17:33:24 UTC (RELENG_4_9, 4.9-RELEASE-p11)
                2004-06-30 17:32:24 UTC (RELENG_4_8, 4.8-RELEASE-p24)
CVE Name:       CAN-2004-0602
FreeBSD only:   YES

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit>.

I.   Background

FreeBSD is binary-compatible with the Linux operating system through a
loadable kernel module/optional kernel component.

II.  Problem Description

A programming error in the handling of some Linux system calls may
result in memory locations being accessed without proper validation.

III. Impact

It may be possible for a local attacker to read and/or overwrite
portions of kernel memory, resulting in disclosure of sensitive
information or potential privilege escalation.  A local attacker can
cause a system panic.

IV.  Workaround

The only known workaround is to disable the linux binary compatibility 
layer and prevent it from being (re)loaded.  Note that step (a) must be
performed before step (b).

a) To prevent the linux compatibility layer being (re)loaded, remove the
/boot/kernel/linux.ko file (on FreeBSD 5.x) or the /modules/linux.ko
file (on FreeBSD 4.x), and add or change the following line in

linux_enable="NO"       # Linux binary compatibility loaded at startup (or NO).

Add or change the following lines in /boot/loader.conf:

linux_load="NO"                 # Linux emulation

In addition, remove any linprocfs file system listed in /etc/fstab.

b) To disable the linux binary compatibility layer, first determine if
it is loaded:

# kldstat -v | grep linuxelf

If no output is produced, the linux compatibility layer is not loaded;
stop here.

If the linux compatibility layer is loaded, determine if it is compiled
into the kernel or loaded as a module:

# kldstat | grep linux.ko

If no output is produced, the linux compatibility layer is compiled
into the kernel.  Remove the line

options         COMPAT_LINUX

from your kernel configuration file and recompile the kernel as
described in> and reboot the

If output is produced, then the linux compatibility layer is loaded as
a kernel module.  If the module is not currently being used (by a
process running under linux emulation, for example) then it may be
possible to unload it:

# kldunload linux
# kldstat | grep linux.ko

If this does not successfully unload the module, reboot the system.

V.   Solution

Perform one of the following:

1) Upgrade your vulnerable system to 4-STABLE; or to the RELENG_5_2,
RELENG_4_10, RELENG_4_9, or RELENG_4_8 security branch dated after the
correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 4.8, 4.9,
4.10 and 5.2 systems.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

[FreeBSD 5.2]
# fetch
# fetch

[FreeBSD 4.8, 4.9, 4.10]
# fetch
# fetch

b) Apply the patch.

# cd /usr/src
# patch < /path/to/patch

c) Recompile your kernel as described in> and reboot the

VI.  Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

Branch                                                           Revision
- -------------------------------------------------------------------------
- -------------------------------------------------------------------------

< Prev   Next >


Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2015 Guardian Digital, Inc. All rights reserved.