Bug 118123 - kdm accesses /dev/mem
Summary: kdm accesses /dev/mem
Status: CLOSED DUPLICATE of bug 118051
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase (Show other bugs)
(Show other bugs)
Version: 2
Hardware: All Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2004-03-12 05:56 UTC by Russell Coker
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 19:01:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Russell Coker 2004-03-12 05:56:11 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.2; Linux) (KHTML, like Gecko)

Description of problem:
audit(1079007629.554:0): avc:  denied  { read } for  pid=2098 exe=/usr/bin/kdm name=mem dev=hda2 ino=2683359 scontext=system_u:system_r:xdm_t tcontext=system_u:object_r:memory_device_t tclass=chr_file

Above is an AVC message reported by a Fedora SE Linux user.  It shows that kdm is accessing /dev/mem.  I believe that this is the old "use kernel memory as source of random numbers" thing, it should be replaced by use of /dev/random.  There is no reason why kdm (or any xdm type program) should directly access /dev/mem.

Allowing kdm to access /dev/mem allows it to entirely break the system's security if it is compromised.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Just run kdm.  It's easy to observe on SE Linux, but when not running SE Linux strace should show it.

Additional info:

Comment 1 Aleksey Nogin 2004-03-12 06:21:15 UTC

*** This bug has been marked as a duplicate of 118051 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:01:56 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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