Bug 460863 - kernel: devmem: add range_is_allowed() check to mmap_mem() [rhel-4.5.z]
Summary: kernel: devmem: add range_is_allowed() check to mmap_mem() [rhel-4.5.z]
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.5.z
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Vitaly Mayatskikh
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On: 460857
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-02 04:57 UTC by Eugene Teo (Security Response)
Modified: 2009-06-15 11:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-02 12:52:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.