Bug 671243 - SELinux is preventing /usr/bin/nautilus from 'mmap_zero' accesses on the memprotect Unknown.
Summary: SELinux is preventing /usr/bin/nautilus from 'mmap_zero' accesses on the memp...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 14
Hardware: i386
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: setroubleshoot_trace_hash:af06cf4f1c0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-20 20:41 UTC by roman
Modified: 2011-03-11 15:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-11 15:29:58 UTC
Type: ---


Attachments (Terms of Use)

Description roman 2011-01-20 20:41:04 UTC
SELinux is preventing /usr/bin/nautilus from 'mmap_zero' accesses on the memprotect Unknown.

*****  Plugin mmap_zero (53.1 confidence) suggests  **************************

If you do not think /usr/bin/nautilus should need to mmap low memory in the kernel.
Then you may be under attack by a hacker, this is a very dangerous access.
Do
contact your security administrator and report this issue.

*****  Plugin catchall_boolean (42.6 confidence) suggests  *******************

If you want to control the ability to mmap a low area of the address space, as configured by /proc/sys/kernel/mmap_min_addr.
Then you must tell SELinux about this by enabling the 'mmap_low_allowed' boolean.
Do
setsebool -P mmap_low_allowed 1

*****  Plugin catchall (5.76 confidence) suggests  ***************************

If you believe that nautilus should be allowed mmap_zero access on the Unknown memprotect by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep nautilus /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1
                              023
Target Context                unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1
                              023
Target Objects                Unknown [ memprotect ]
Source                        nautilus
Source Path                   /usr/bin/nautilus
Port                          <Неизвестно>
Host                          (removed)
Source RPM Packages           nautilus-2.32.2.1-1.fc14
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.7-19.fc14
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 2.6.35.10-74.fc14.i686
                              #1 SMP Thu Dec 23 16:17:40 UTC 2010 i686 i686
Alert Count                   677
First Seen                    Пнд 17 Янв 2011 16:03:18
Last Seen                     Пнд 17 Янв 2011 16:06:17
Local ID                      d2a7c981-946e-4480-89d6-a32aff4be37e

Raw Audit Messages
type=AVC msg=audit(1295276777.430:27080): avc:  denied  { mmap_zero } for  pid=2084 comm="nautilus" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=memprotect

nautilus,unconfined_t,unconfined_t,memprotect,mmap_zero
type=SYSCALL msg=audit(1295276777.430:27080): arch=i386 syscall=mmap2 success=no exit=EACCES a0=0 a1=100000 a2=0 a3=4022 items=0 ppid=1947 pid=2084 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=1 comm=nautilus exe=/usr/bin/nautilus subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=(null)
nautilus,unconfined_t,unconfined_t,memprotect,mmap_zero

#============= unconfined_t ==============
#!!!! This avc can be allowed using the boolean 'mmap_low_allowed'

allow unconfined_t self:memprotect mmap_zero;

Comment 1 Daniel Walsh 2011-01-20 21:31:18 UTC
Something very strange going on, on your machine.

This access should not be needed.

I would yum update and see if this goes away.  It is not an access you want to give out.


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