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.
Bug 1160174 - SELinux is preventing /usr/sbin/brctl from 'read' accesses on the file .
Summary: SELinux is preventing /usr/sbin/brctl from 'read' accesses on the file .
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.1
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: Milos Malik
URL:
Whiteboard: abrt_hash:e8f2805f0eeec2d61adcbca237f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-04 08:59 UTC by David Jaša
Modified: 2015-03-05 10:46 UTC (History)
6 users (show)

Fixed In Version: selinux-policy-3.13.1-7.el7.noarch
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 10:46:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
grep -B 100 -A 50 /usr/sbin/brctl /var/log/messages (28.62 KB, text/plain)
2014-11-04 14:59 UTC, David Jaša 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0458 0 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2015-03-05 15:17:00 UTC

Description David Jaša 2014-11-04 08:59:08 UTC 
Description of problem:
SELinux is preventing /usr/sbin/brctl from 'read' accesses on the file .

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that brctl should be allowed read access on the  file 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 brctl /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:brctl_t:s0-s0:c0.c1023
Target Context                system_u:object_r:proc_t:s0
Target Objects                 [ file ]
Source                        brctl
Source Path                   /usr/sbin/brctl
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           bridge-utils-1.5-9.el7.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-7.el7.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 3.10.0-196.el7.x86_64 #1 SMP Tue
                              Oct 28 11:16:22 EDT 2014 x86_64 x86_64
Alert Count                   1
First Seen                    2014-11-04 09:57:44 CET
Last Seen                     2014-11-04 09:57:44 CET
Local ID                      117024ea-bf40-4bf2-8b5d-fab4f44977f9

Raw Audit Messages
type=AVC msg=audit(1415091464.613:2904): avc:  denied  { read } for  pid=10675 comm="brctl" name="meminfo" dev="proc" ino=4026532039 scontext=system_u:system_r:brctl_t:s0-s0:c0.c1023 tcontext=system_u:object_r:proc_t:s0 tclass=file


type=SYSCALL msg=audit(1415091464.613:2904): arch=x86_64 syscall=open success=no exit=EACCES a0=7fcea4943789 a1=80000 a2=1b6 a3=7fff83f67770 items=0 ppid=10674 pid=10675 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=brctl exe=/usr/sbin/brctl subj=system_u:system_r:brctl_t:s0-s0:c0.c1023 key=(null)

Hash: brctl,brctl_t,proc_t,file,read

Additional info:
reporter:       libreport-2.1.11
hashmarkername: setroubleshoot
kernel:         3.10.0-196.el7.x86_64
type:           libreport
Comment 2 Milos Malik 2014-11-04 09:14:25 UTC 
Who runs the brctl tool? It seems to be executed from an init script or systemd unit file.
Comment 3 David Jaša 2014-11-04 14:59:25 UTC 
Created attachment 953646 [details]
grep -B 100 -A 50 /usr/sbin/brctl /var/log/messages

(In reply to Milos Malik from comment #2)
> Who runs the brctl tool? It seems to be executed from an init script or
> systemd unit file.

I have no idea. The selinux warning just pops up from time to time without any trace of caller in the logs (snippet of messages is attached)
Comment 4 Miroslav Grepl 2014-11-05 09:49:08 UTC 
commit 92348c5dc13cd53385808955d03e6a004484561c
Author: Miroslav Grepl <mgrepl>
Date:   Wed Nov 5 10:48:34 2014 +0100

    Allow brctl to read meminfo.
Comment 8 errata-xmlrpc 2015-03-05 10:46:29 UTC 
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.

https://rhn.redhat.com/errata/RHBA-2015-0458.html
Note You need to log in before you can comment on or make changes to this bug.