Bug 138534 - CVE-2004-1056 insufficient locking checks in DRM code
Summary: CVE-2004-1056 insufficient locking checks in DRM code
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Don Howard
QA Contact: Brian Brock
URL:
Whiteboard: impact=moderate,public=20041109
Depends On:
Blocks: 156320
TreeView+ depends on / blocked
 
Reported: 2004-11-09 20:00 UTC by Josh Bressers
Modified: 2007-11-30 22:07 UTC (History)
7 users (show)

Fixed In Version: RHSA-2005-663
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-28 14:32:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Proposed patch for this issue. (7.86 KB, patch)
2004-11-17 16:19 UTC, Josh Bressers 		no flags Details | Diff
rediff of above patch for RHEL3 (6.66 KB, patch)
2005-05-18 18:07 UTC, Don Howard 		no flags Details | Diff
updated drm locking patch for rhel3 (7.13 KB, patch)
2005-06-15 16:52 UTC, Don Howard 		no flags Details | Diff
Show Obsolete (1) View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:663 0 qe-ready SHIPPED_LIVE Important: Updated kernel packages available for Red Hat Enterprise Linux 3 Update 6 2005-09-28 04:00:00 UTC

Description Josh Bressers 2004-11-09 20:00:07 UTC 
Stefan Dirsch reported to the freedesktop.org bugzilla an issue with
permissions within the DRM code.

See this url for more information, including a patch.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1803

This issue should also affect RHEL2.1
Comment 1 Josh Bressers 2004-11-09 20:04:41 UTC 
This issue probably also affects RHEL4.
Comment 2 Mike A. Harris 2004-11-10 20:39:49 UTC 
DRM source is part of both the kernel and X.  We build it in the
kernel.  Reassigning to kernel component.
Comment 3 Ernie Petrides 2004-11-15 22:00:30 UTC 
Peter/Tim, I'm assuming that DaveJ is too busy with RHEL4 to take on
this bug.  But I don't know who else covers this area.  I'm sticking
PeterM with this for now (presumably for appropriate reassignment).

Josh, the URL in your initial comment times out.  Could you please
provide another pointer?  Thanks in advance.
Comment 4 Josh Bressers 2004-11-15 22:18:52 UTC 
freedesktop.org seems to be down.  I don't have a different source for
this information, hopefully the site comes back alive soon.  If not
I'll do some digging.
Comment 5 Mark J. Cox 2004-11-17 10:06:06 UTC 
Freedesktop.org was compromised. Google has it in cache:
http://216.239.39.104/search?q=cache:ZUUhmlXH98UJ:https://freedesktop.org/bugzilla/show_bug.cgi%3Fid%3D1803+&hl=en&start=1

Google doesn't have a cache of the patch
Comment 6 Josh Bressers 2004-11-17 16:19:03 UTC 
Created attachment 106893 [details]
Proposed patch for this issue.
Comment 7 Josh Bressers 2005-01-06 18:41:29 UTC 
Ping on this issue.
Comment 8 Mark J. Cox 2005-02-23 10:58:29 UTC 
The patch proposed is missing the definition of the LOCK_TEST..., see
instead 
http://mirror.clarkson.edu/pub/distributions/gentoo-portage/sys-kernel/gentoo-sources/files/gentoo-sources-2.4.20-CAN-2004-1056.patch
Comment 9 Ernie Petrides 2005-04-28 02:37:35 UTC 
Reassigning to Don.
Comment 10 Don Howard 2005-05-18 18:07:42 UTC 
Created attachment 114527 [details]
rediff of above patch for RHEL3
Comment 12 Don Howard 2005-06-15 16:52:27 UTC 
Created attachment 115490 [details]
updated drm locking patch for rhel3
Comment 13 Ernie Petrides 2005-06-17 22:51:22 UTC 
A fix for this problem has just been committed to the RHEL3 U6
patch pool this evening (in kernel version 2.4.21-32.9.EL).
Comment 20 Red Hat Bugzilla 2005-09-28 14:32:30 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-663.html
Note You need to log in before you can comment on or make changes to this bug.