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 4 product line. The current stable release is 4.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 144471

Summary:	CAN-2005-0176 unlock someone elses ipc memory
Product:	Red Hat Enterprise Linux 4	Reporter:	Josh Bressers <bressers>
Component:	kernel	Assignee:	Dave Jones <davej>
Status:	CLOSED ERRATA	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	jbaron, lwoodman, peterm, pfrields, riel, sct
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	public=20041124,impact=moderate
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-02-18 17:20:52 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:
Bug Depends On:
Bug Blocks:	144195

Description Josh Bressers 2005-01-07 13:49:33 UTC

*** This bug has been split off bug 142802 ***

------- Original comment by Mark J. Cox (Security Response Team) on 2004.12.14
10:34 -------

Reported on lkml a flaw that allows you to unlock someone
elses ipc memory (hence crossing permission boundary).

http://marc.theaimsgroup.com/?l=linux-kernel&m=110132782610477
http://marc.theaimsgroup.com/?l=linux-kernel&m=110137276318105

"In 2.6.8, the only processes that could lock shared memory segments
were those with CAP_IPC_LOCK.  Unprivileged processes did not get a
look in."

Looks like this is 2.6.9 (Arjan says since the fixed rhel3 mlock stuff
got merged it might be there too)

Comment 1 Josh Bressers 2005-02-18 17:20:52 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-092.html