Hide Forgot
libreport version: 2.0.8 executable: /usr/bin/python hashmarkername: setroubleshoot kernel: 3.2.3-2.fc16.x86_64 reason: SELinux is preventing /usr/sbin/monitor-get-edid-using-vbe from 'mmap_zero' accesses on the None . time: Tue 07 Feb 2012 17:18:12 CET description: :SELinux is preventing /usr/sbin/monitor-get-edid-using-vbe from 'mmap_zero' accesses on the None . : :***** Plugin mmap_zero (91.4 confidence) suggests ************************** : :If you do not think /usr/sbin/monitor-get-edid-using-vbe 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 monitor-get-edid-using-vbe should be allowed mmap_zero access on the <Unknown> 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 monitor-get-edi /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 [ None ] :Source monitor-get-edi :Source Path /usr/sbin/monitor-get-edid-using-vbe :Port <Unknown> :Host (removed) :Source RPM Packages monitor-edid-3.0-3.fc15.x86_64 :Target RPM Packages :Policy RPM selinux-policy-3.10.0-75.fc16.noarch :Selinux Enabled True :Policy Type targeted :Enforcing Mode Permissive :Host Name (removed) :Platform Linux (removed) 3.2.3-2.fc16.x86_64 #1 SMP Fri Feb 3 : 20:08:08 UTC 2012 x86_64 x86_64 :Alert Count 2 :First Seen Tue 07 Feb 2012 17:15:09 CET :Last Seen Tue 07 Feb 2012 17:16:05 CET :Local ID d5e23747-4757-4e50-ba7d-ddcbf8a9fb43 : :Raw Audit Messages :type=AVC msg=audit(1328631365.741:352): avc: denied { mmap_zero } for pid=12733 comm="monitor-get-edi" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=memprotectnode=(removed) type=SYSCALL msg=audit(1328631365.741:352): arch=c000003e syscall=9 success=yes exit=61440 a0=f000 a1=502 a2=7 a3=11 items=0 ppid=12732 pid=12733 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts1 ses=2 comm="monitor-get-edi" exe="/usr/sbin/monitor-get-edid-using-vbe" subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=(null) : : :Hash: monitor-get-edi,unconfined_t,unconfined_t,None,mmap_zero : :audit2allow : : :audit2allow -R : :
This happens after one of the latest selinux-policy updates monitor-get-edid-using-vbe is used to extract the Monitor EDID on select systems or configurations. For instance it gets called by monitor-edid when run as root. I have some scripts that run monitor-edid to determine the attached displays, and to suggest which ICM files to use. This breaks with the latest policy update.
mmap_zero is a very dangerous access and almost assuredly not needed. Only other apps that we are aware of that request this access are vbetool and wine, for old DOS apps.
http://eparis.livejournal.com/891.html Explains the access.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Same issue with F17
This program is calling: mmap(0xf000, 0x502, PROT_READ | PROT_WRITE | PROT_EXECUTE, MAP_SHARED | MAP_FIXED) The lowest allowed fixed address is 0x10000 This program should either up the base or should stop using MAP_FIXED. This is NOT an selinux bug.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.