Description of problem: Version-Release number of selected component (if applicable): selinux-policy-minimum-2.4.6-306.el5 selinux-policy-targeted-2.4.6-306.el5 selinux-policy-devel-2.4.6-306.el5 selinux-policy-strict-2.4.6-306.el5 selinux-policy-mls-2.4.6-306.el5 selinux-policy-2.4.6-306.el5 How reproducible: not sure Actual results: ---- time->Tue May 31 10:01:01 2011 type=SYSCALL msg=audit(1306850461.963:83): arch=c000003e syscall=2 success=no exit=-13 a0=406a67 a1=0 a2=331e953990 a3=63656420494d4420 items=0 ppid=3054 pid=3057 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="mcelog" exe="/usr/sbin/mcelog" subj=system_u:system_r:system_crond_t:s0-s15:c0.c1023 key=(null) type=AVC msg=audit(1306850461.963:83): avc: denied { read } for pid=3057 comm="mcelog" name="mcelog" dev=tmpfs ino=3066 scontext=system_u:system_r:system_crond_t:s0-s15:c0.c1023 tcontext=system_u:object_r:printk_device_t:s15:c0.c1023 tclass=chr_file ---- Expected results: no AVCs
I though 2 same AVCs appeared but this is different from the previous one: ---- time->Tue May 31 10:01:01 2011 type=SYSCALL msg=audit(1306850461.963:82): arch=c000003e syscall=2 success=no exit=-13 a0=408270 a1=0 a2=3 a3=2d items=0 ppid=3054 pid=3057 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="mcelog" exe="/usr/sbin/mcelog" subj=system_u:system_r:system_crond_t:s0-s15:c0.c1023 key=(null) type=AVC msg=audit(1306850461.963:82): avc: denied { read } for pid=3057 comm="mcelog" name="mem" dev=tmpfs ino=2011 scontext=system_u:system_r:system_crond_t:s0-s15:c0.c1023 tcontext=system_u:object_r:memory_device_t:s15:c0.c1023 tclass=chr_file ----
The problem is we do not have mcelog policy in RHEL5. Not sure if mcelog is supposed to be run on an MLS box though.
I think I could add it to make this working. We have it also in Fedora/RHEL6
ok
Fixed in selinux-policy-2.4.6-320.el5
These are specific for RHEL5 which we need to add.
Fixed in selinux-policy-2.4.6-324.el5
Fixed in selinux-policy-2.4.6-326.el5
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0158.html