Bug 460863

Summary:	kernel: devmem: add range_is_allowed() check to mmap_mem() [rhel-4.5.z]
Product:	Red Hat Enterprise Linux 4	Reporter:	Eugene Teo (Security Response) <eteo>
Component:	kernel	Assignee:	Vitaly Mayatskikh <vmayatsk>
Status:	CLOSED WONTFIX	QA Contact:	Martin Jenner <mjenner>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.5.z	CC:	davej, dhoward, lwang, mgahagan, security-response-team, vmayatsk
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-10-02 12:52:17 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:	460857
Bug Blocks:

Description Eugene Teo (Security Response) 2008-09-02 04:57:07 UTC

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

Description of problem:
Eugene Teo discovered that range_is_allowed() check is only added in
{read,write}_mem(). It is possible for an illegitimate application to bypass
these checks, and access /dev/mem beyond the 1M limit by calling mmap_mem()
instead.

--- Additional comment from eteo on 2008-09-02 00:07:32 EDT ---

This appears to be fixed in upstream since commit e2beb3eae.

Comment 1 RHEL Program Management 2008-09-02 08:23:50 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 2 Jiri Skrabal 2008-10-02 12:52:17 UTC

Closing this BZ. We do not have a business case for 4.5.z backport.