Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Were there any python exceptions recorded during the sos run that triggered this AVC?
The only way I can see sos leaking an fd to sos_commands/networking/brctl_show is if there's an unhandled exception while reading from this file.
I also don't understand why dmesg is attempting to access this file. Anyway, this has never been seen on "normal" sos runs outside abrtd (and probably can't happen as they normally run unconfined in a root session) so I think abrt needs to look at how it's running the command to avoid it.
Can't find a reliable reproducer so I think it's not so critical - moving to 6.4.
Comment 9RHEL Program Management
2012-07-10 08:32:17 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 10RHEL Program Management
2012-07-10 23:02:45 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 11RHEL Program Management
2012-12-14 08:53:43 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Description of problem: Version-Release number of selected component (if applicable): selinux-policy-3.7.19-109.el6.noarch How reproducible: sometimes Steps to Reproduce: * it's very likely that the AVC was caused by following automated test: /CoreOS/sos/Sanity/report-size Actual results (seen on different machines) ---- time->Fri Sep 9 19:24:01 2011 type=SYSCALL msg=audit(1315610641.241:998205): arch=c000003e syscall=59 success=yes exit=0 a0=170f8f0 a1=170eda0 a2=170e880 a3=10 items=0 ppid=1889 pid=2129 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dmesg" exe="/bin/dmesg" subj=system_u:system_r:dmesg_t:s0-s0:c0.c1023 key=(null) type=AVC msg=audit(1315610641.241:998205): avc: denied { read } for pid=2129 comm="dmesg" path="/var/spool/abrt/pyhook-2011-09-09-19:23:55-1842/dell-pe2950-01-2011090919231315610636/sos_commands/networking/brctl_show" dev=dm-0 ino=1183316 scontext=system_u:system_r:dmesg_t:s0-s0:c0.c1023 tcontext=system_u:object_r:abrt_var_cache_t:s0 tclass=file ---- Expected results: * no AVCs