SELinux is preventing /usr/bin/brasero from using the 'execstack' accesses on a process. ***** Plugin allow_execstack (53.1 confidence) suggests ******************** If you do not think /usr/bin/brasero should need to map stack memory that is both writable and executable. Then you need to report a bug. This is a potentially dangerous access. Do contact your security administrator and report this issue. ***** Plugin catchall_boolean (42.6 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 (5.76 confidence) suggests *************************** If you believe that brasero should be allowed execstack access on processes labeled unconfined_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 /usr/bin/brasero /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 [ process ] Source brasero Source Path /usr/bin/brasero Port <Unbekannt> Host (removed) Source RPM Packages brasero-2.32.0-1.fc14 Target RPM Packages Policy RPM selinux-policy-3.9.7-16.fc14 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.35.9-64.fc14.i686 #1 SMP Fri Dec 3 12:35:42 UTC 2010 i686 i686 Alert Count 61 First Seen Fr 17 Dez 2010 08:06:44 CET Last Seen Fr 17 Dez 2010 08:25:05 CET Local ID 6c676640-644f-4472-87cb-ca09fa95f60f Raw Audit Messages type=AVC msg=audit(1292570705.488:30490): avc: denied { execstack } for pid=2608 comm="brasero" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=process brasero,unconfined_t,unconfined_t,process,execstack type=SYSCALL msg=audit(1292570705.488:30490): arch=i386 syscall=mprotect success=no exit=EACCES a0=bfcdf000 a1=1000 a2=1000007 a3=bfcde58c items=0 ppid=1 pid=2608 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=1 comm=brasero exe=/usr/bin/brasero subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=(null) brasero,unconfined_t,unconfined_t,process,execstack #============= unconfined_t ============== #!!!! This avc can be allowed using the boolean 'allow_execstack' allow unconfined_t self:process execstack;
Why does brasero need execstack?
as of March 4 2011 Brasero has not been updated, and of course still has this problem. How would one find out where in the brasero execution path is this happening? Is there a way to run GDB to trigger a breakpoint on a SELinux violation?
This is probably not a problem with braserro but with a shared library it is using. Read the bug I am closing this as a dup of to find the shared library. *** This bug has been marked as a duplicate of bug 652297 ***