Bug 702942 - SELinux is preventing /usr/bin/Xorg (deleted) from using the 'execmem' accesses on a process.
Summary: SELinux is preventing /usr/bin/Xorg (deleted) from using the 'execmem' access...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: setroubleshoot_trace_hash:85e799061e5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-08 14:41 UTC by Tom
Modified: 2011-05-09 15:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-09 15:43:12 UTC
Type: ---


Attachments (Terms of Use)

Description Tom 2011-05-08 14:41:48 UTC
SELinux is preventing /usr/bin/Xorg (deleted) from using the 'execmem' accesses on a process.

*****  Plugin catchall_boolean (32.5 confidence) suggests  *******************

If you want to allows XServer to execute writable memory
Then you must tell SELinux about this by enabling the 'allow_xserver_execmem' boolean.
Do
setsebool -P allow_xserver_execmem 1

*****  Plugin catchall_boolean (32.5 confidence) suggests  *******************

If you want to allow unconfined executables to make their stack executable.  This should never, ever be necessary. Probably indicates a badly coded executable, but could indicate an attack. This executable should be reported in bugzilla
Then you must tell SELinux about this by enabling the 'allow_execstack' boolean.
Do
setsebool -P allow_execstack 1

*****  Plugin catchall_boolean (32.5 confidence) suggests  *******************

If you want to allow unconfined executables to map a memory region as both executable and writable, this is dangerous and the executable should be reported in bugzilla
Then you must tell SELinux about this by enabling the 'allow_execmem' boolean.
Do
setsebool -P allow_execmem 1

*****  Plugin catchall (4.5 confidence) suggests  ****************************

If you believe that Xorg (deleted) should be allowed execmem access on processes labeled xserver_t 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 X /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:xserver_t:s0-s0:c0.c1023
Target Context                system_u:system_r:xserver_t:s0-s0:c0.c1023
Target Objects                Unknown [ process ]
Source                        X
Source Path                   /usr/bin/Xorg (deleted)
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           xorg-x11-server-Xorg-1.10.1-14.fc15
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.16-23.fc15
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 2.6.38.5-22.fc15.x86_64 #1 SMP Mon
                              May 2 19:28:55 UTC 2011 x86_64 x86_64
Alert Count                   2
First Seen                    Sun 08 May 2011 10:25:11 AM EDT
Last Seen                     Sun 08 May 2011 10:36:30 AM EDT
Local ID                      65c258fc-e84e-4070-8d1a-7a3becc0334c

Raw Audit Messages
type=AVC msg=audit(1304865390.84:231): avc:  denied  { execmem } for  pid=32503 comm="X" scontext=system_u:system_r:xserver_t:s0-s0:c0.c1023 tcontext=system_u:system_r:xserver_t:s0-s0:c0.c1023 tclass=process


type=SYSCALL msg=audit(1304865390.84:231): arch=x86_64 syscall=mmap success=no exit=EACCES a0=0 a1=80000 a2=7 a3=22 items=0 ppid=1636 pid=32503 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty7 ses=4294967295 comm=X exe=/usr/bin/Xorg subj=system_u:system_r:xserver_t:s0-s0:c0.c1023 key=(null)

Hash: X,xserver_t,xserver_t,process,execmem

audit2allow

#============= xserver_t ==============
#!!!! This avc can be allowed using one of the these booleans:
#     allow_xserver_execmem, allow_execstack, allow_execmem

allow xserver_t self:process execmem;

audit2allow -R

#============= xserver_t ==============
#!!!! This avc can be allowed using one of the these booleans:
#     allow_xserver_execmem, allow_execstack, allow_execmem

allow xserver_t self:process execmem;

Comment 1 Daniel Walsh 2011-05-09 15:43:12 UTC
Did you read the alert, it tells you what to do.


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