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 2.1 product line. 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 126122

Summary: CAN-2004-0495 Sparse security fixes backported for 2.4 kernel
Product: Red Hat Enterprise Linux 2.1 Reporter: Mark J. Cox <mjc>
Component: kernelAssignee: Jason Baron <jbaron>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: knoel, riel
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-06-18 21:21:57 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-06-16 11:25:17 UTC 
Recently committed to the 2.6 kernel were enhancements from Al Viro
that enabled the Sparse source code checking tool to check for a
certain class kernel bugs. This class of bugs can lead to privilege
escalation vulnerabilities.  Some of these fixes also apply to the 2.4
kernel and have been backported.  Specifically affecting the RHEL
2.1AS/WS/ES kernels:

1. Direct write to a user-supplied address which can lead to privilege
escalation in the mpu401 and pss sound drivers.

2. Direct read of a user-supplied address can cause information leak
from kernel memory in the airo wireless driver, and the mpu401 and pss
sound drivers.

3. Deadlock in the msnd sound driver.
Comment 1 Mark J. Cox 2004-06-18 21:21:57 UTC 
An errata 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-2004-260.html