Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 143866

Summary:	CAN-2004-1237 kernel panic caused by auditd
Product:	Red Hat Enterprise Linux 3	Reporter:	Josh Bressers <bressers>
Component:	kernel	Assignee:	Charlie Bennett <ccb>
Status:	CLOSED ERRATA	QA Contact:	Jay Turner <jturner>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.0	CC:	peterm, petrides, security-response-team, srevivo
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	impact=important,public=20040910
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-01-18 23:52:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Josh Bressers 2004-12-30 13:04:22 UTC

Wade Holmes reported to secalert on 2004-12-28 a bug in auditd that
can cause a kernel panic.

An easily repeatable and exploitable problem with laus/auditd has been
discovered on RedHat Enterprise WS.  It has been tested on IA-32 and
x86_64, others running auditd may also be vulnerable.

To cause a kernel panic/oops execute the open() call under an
user/global execute only directory from cron.  Any user with access to
cron can initiate the panic.  Example:

User's crontab:
0 5 * * *       /tmp/folder/panic.pl

contents of panic.pl:
#!/usr/bin/perl
# this file does not have to exist.
$file = "/tmp/foo";
open($file);

permissions of /tmp/folder:
dr-x--x--x



If this is a kernel issue rather than a problem with auditd, please
refile this bug.

This issue does not seem to affect anything other than RHEL3.

Comment 4 Peter Martuccelli 2005-01-04 18:08:52 UTC

This is already fixed in U5, marking entry as a duplicate of BZ #
141996.  The parent BZ # is 132245.

*** This bug has been marked as a duplicate of 141996 ***

Comment 5 Ernie Petrides 2005-01-04 21:01:05 UTC

Josh, this can't be embargoed.  We've already made the fix in U5,
and although U5 has not yet been released, kernels with the fix
have already been given to key partners/customers for testing
other U5 fixes.

Comment 6 Josh Bressers 2005-01-04 21:04:49 UTC

Ernie, That's fair.  I wanted to be sure.  Removing embargo.

Comment 7 Ernie Petrides 2005-01-13 03:53:44 UTC

The fix for this problem has also been committed to the RHEL3 E5
patch pool this evening (in kernel version 2.4.21-27.0.2.EL).

Comment 8 David Lawrence 2005-01-18 23:52:36 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2005-043.html