Bug 144389 - CAN-2004-1056 insufficient locking checks in DRM code
CAN-2004-1056 insufficient locking checks in DRM code
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel (Show other bugs)
2.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Don Howard
Brian Brock
impact=moderate,public=20041109
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-01-06 13:46 EST by Josh Bressers
Modified: 2007-11-30 17:06 EST (History)
4 users (show)

See Also:
Fixed In Version: RHSA-2005-551
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-25 09:16:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Josh Bressers 2005-01-06 13:46:30 EST
*** This bug has been split off bug 138534 ***

------- Original comment by Josh Bressers (Security Response Team) on 2004.11.09
15:00 -------

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 Jason Baron 2005-03-31 14:35:39 EST
hmmm, this isn't in upstream 2.4, i wonder why.
Comment 2 Don Howard 2005-07-08 03:54:23 EDT
A patch addressing this issue has been committed to the RHEL2.1 tree. (kernel
version 2.4.9-e64.1)
Comment 5 Red Hat Bugzilla 2005-08-25 09:16:55 EDT
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-551.html

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