Bug 512642

Summary:	kernel: security: implement mmap_min_addr infrastructure [rhel-3]
Product:	Red Hat Enterprise Linux 3	Reporter:	Eugene Teo (Security Response) <eteo>
Component:	kernel	Assignee:	Don Howard <dhoward>
Status:	CLOSED ERRATA	QA Contact:	Martin Jenner <mjenner>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.9	CC:	dhoward, eparis, jmorris, lwang, phan, security-response-team
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	512638	Environment:
Last Closed:	2009-11-03 22:00:48 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:	512638
Bug Blocks:

Description Eugene Teo (Security Response) 2009-07-20 06:00:10 UTC

+++ This bug was initially created as a clone of Bug #512638 +++

Description of problem:
This patch removes the dependency of mmap_min_addr on CONFIG_SECURITY. It also sets a default mmap_min_addr of 4096.

mmapping of addresses below 4096 will only be possible for processes with CAP_SYS_RAWIO.

Upstream commit:
http://git.kernel.org/linus/e0a94c2a63f2644826069044649669b5e7ca75d3

Comment 1 Eric Paris 2009-07-20 17:33:11 UTC

Does RHEL3 even have CONFIG_SECURITY?  I haven't seen a RHEL3 backport, but anything that works is going to have to deal with this issue since we don't have LSMs in RHEL3.  This should probably just be closed and dealt with in the bug that is backporting the mmap_min_addr support.

Comment 6 Don Howard 2009-10-16 18:50:03 UTC

A patch for this issue has been included in build 2.4.21-61.EL.

Comment 12 errata-xmlrpc 2009-11-03 22:00:48 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 therefore 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-2009-1550.html