Bug 126122 - CAN-2004-0495 Sparse security fixes backported for 2.4 kernel
Summary: CAN-2004-0495 Sparse security fixes backported for 2.4 kernel
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 2.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jason Baron
QA Contact: Brian Brock
Keywords: Security
Depends On:
TreeView+ depends on / blocked
Reported: 2004-06-16 11:25 UTC by Mark J. Cox
Modified: 2013-03-06 05:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-18 21:21:57 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2004:260 normal SHIPPED_LIVE Important: kernel security update 2004-06-18 04:00:00 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.