SELinux is preventing /usr/bin/eu-unstrip from 'mmap_zero' accesses on the memprotect Unknown. ***** Plugin mmap_zero (91.4 confidence) suggests ************************** If you do not think /usr/bin/eu-unstrip 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 (9.59 confidence) suggests *************************** If you believe that eu-unstrip 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 eu-unstrip /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:abrt_t:s0-s0:c0.c1023 Target Context system_u:system_r:abrt_t:s0-s0:c0.c1023 Target Objects Unknown [ memprotect ] Source eu-unstrip Source Path /usr/bin/eu-unstrip Port <Unknown> Host (removed) Source RPM Packages elfutils-0.152-1.fc14 Target RPM Packages Policy RPM selinux-policy-3.9.7-40.fc14 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.35.13-91.fc14.i686 #1 SMP Tue May 3 13:36:36 UTC 2011 i686 i686 Alert Count 65 First Seen Tue 24 May 2011 01:51:15 PM CDT Last Seen Tue 24 May 2011 04:07:28 PM CDT Local ID 63e4d054-9fff-4fd4-ab9e-2524d8a283c7 Raw Audit Messages type=AVC msg=audit(1306271248.95:20762): avc: denied { mmap_zero } for pid=30457 comm="eu-unstrip" scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tclass=memprotect type=SYSCALL msg=audit(1306271248.95:20762): arch=i386 syscall=mmap2 success=no exit=EACCES a0=0 a1=3930 a2=3 a3=2 items=0 ppid=30456 pid=30457 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=eu-unstrip exe=/usr/bin/eu-unstrip subj=system_u:system_r:abrt_t:s0-s0:c0.c1023 key=(null) Hash: eu-unstrip,abrt_t,abrt_t,memprotect,mmap_zero audit2allow #============= abrt_t ============== allow abrt_t self:memprotect mmap_zero; audit2allow -R #============= abrt_t ============== allow abrt_t self:memprotect mmap_zero;
For this alone i would probably already create a new domain for eu-unstrip.
This is definitely not some thing you want to allow. We do not want to allow any app mmap_zero especially if it is being run by abrt. Applications should not require this access. Only apps I am aware that need it are wine apps.
How was eu-unstrip invoked? What arguments and what files were given?
Looks like a false alarm that eu-unstrip actually needs this to me. Dup of 490753. a2=3 a3=2 Which looks like PROT_READ|PROT_WRITE, MAP_PRIVATE. The kernel is dynamically choosing an address which is too low. I keep meaning to get time to fix the vm from doing this... *** This bug has been marked as a duplicate of bug 490753 ***