Bug 144138

Summary: CAN-2004-1235 isec.pl do_brk() privilege escalation
Product: Red Hat Enterprise Linux 2.1 Reporter: Josh Bressers <bressers>
Component: kernelAssignee: Jim Paradis <jparadis>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 2.1CC: menscher, peterm, riel, security-response-team, wtogami
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: ia64   
OS: Linux   
Whiteboard: reported=20041222,public=20050106,impact=important
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-01-21 15:41:31 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:
Attachments:
Description Flags
isec.pl exploit. See the source for compilation instructions.
none
Proposed patch for this issue. none

Description Josh Bressers 2005-01-04 19:41:29 UTC 
isec.pl reported a missing down() on mmap_sem semaphore whilst calling do_brk;
so if do_brk() sleeps on a kmalloc it may get into a VMA list race - leading to
results similar to the do_brk exploit.
Comment 2 Josh Bressers 2005-01-04 19:48:16 UTC 
Created attachment 109343 [details]
Proposed patch for this issue.
Comment 3 Mark J. Cox 2005-01-10 09:31:48 UTC 
Removing embargo
Comment 8 Damian Menscher 2005-01-16 16:30:40 UTC 
Does this affect RHEL3?  Is a patch coming?  This has been public for
9 days, and your customers are nervous.
Comment 9 Jim Paradis 2005-01-17 20:55:28 UTC 
A fix for this problem has also been committed to the RHEL2.1 U7
patch pool (in kernel version 2.4.18-e.53)
Comment 10 Josh Bressers 2005-01-21 15:41:31 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-017.html