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 127915

Summary: CAN-2004-0138 Verify interpreter arch
Product: Red Hat Enterprise Linux 3 Reporter: Mark J. Cox <mjc>
Component: kernelAssignee: Jim Paradis <jparadis>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: peterm, petrides, riel, security-response-team
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: ia64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-11-17 21:37:05 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 Mark J. Cox 2004-07-15 11:04:27 UTC 
A flaw was found and fixed in 2.6 (and backported to 2.4 on 20040204).
 On ia64 platforms that can allegedly cause a local unprivileged user
to oops the kernel; but others have said that it causes a BUG() and
leaking vma only.

http://linux.bkbits.net:8080/linux-2.6/cset@3f96a083QbCcQgd-bg2Bt2-LMX-QJg
       
http://linux.bkbits.net:8080/linux-2.4/cset@4021346f79nBb-4X_usRikR3Iyb4Vg

Therefore fixed in 2.4.25
Comment 1 Jim Paradis 2004-11-17 01:06:20 UTC 
This fix is slated for the RHEL3-U4 respin taking place 11/16/04

Although reported against ia64, the fix is good for all arches.
Comment 4 Ernie Petrides 2004-11-25 01:27:09 UTC 
The fix for this problem has been committed to both the RHEL3 U4 and the
RHEL3 E4 patch pools (in kernel versions 2.4.21-25.EL and 2.4.21-20.0.1.EL).
Comment 5 Marcel Holtmann 2006-05-31 13:41:09 UTC 
The correct CVE name for this issue is CVE-2004-0138.