Bug 1638754

Summary: SELinux is preventing dbus-broker from 'write' accesses on the fifo_file /run/boltd/power/2.guard.fifo.
Product: [Fedora] Fedora Reporter: Stephen Gallagher <sgallagh>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: dwalsh, fredrik.schon, lvrabec, mgrepl, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f72e78a9d8b11aefb2fea6592d9492621b17da57cd88e484279bc854c57b84e3;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-15 11:25:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stephen Gallagher 2018-10-12 11:45:11 UTC
Description of problem:
SELinux is preventing dbus-broker from 'write' accesses on the fifo_file /run/boltd/power/2.guard.fifo.

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

If you believe that dbus-broker should be allowed write access on the 2.guard.fifo fifo_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:
# ausearch -c 'dbus-broker' --raw | audit2allow -M my-dbusbroker
# semodule -X 300 -i my-dbusbroker.pp

Additional Information:
Source Context                system_u:system_r:system_dbusd_t:s0-s0:c0.c1023
Target Context                system_u:object_r:boltd_var_run_t:s0
Target Objects                /run/boltd/power/2.guard.fifo [ fifo_file ]
Source                        dbus-broker
Source Path                   dbus-broker
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.14.2-36.fc29.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.18.13-300.fc29.x86_64 #1 SMP Wed
                              Oct 10 17:22:50 UTC 2018 x86_64 x86_64
Alert Count                   7
First Seen                    2018-10-11 20:55:26 EDT
Last Seen                     2018-10-12 07:44:33 EDT
Local ID                      e91168df-a421-4c59-b3a0-8a86ade4c6e0

Raw Audit Messages
type=AVC msg=audit(1539344673.249:326): avc:  denied  { write } for  pid=1047 comm="dbus-daemon" path="/run/boltd/power/2.guard.fifo" dev="tmpfs" ino=60923 scontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:boltd_var_run_t:s0 tclass=fifo_file permissive=0


Hash: dbus-broker,system_dbusd_t,boltd_var_run_t,fifo_file,write

Version-Release number of selected component:
selinux-policy-3.14.2-36.fc29.noarch

Additional info:
component:      selinux-policy
reporter:       libreport-2.9.6
hashmarkername: setroubleshoot
kernel:         4.18.13-300.fc29.x86_64
type:           libreport

Comment 1 Fredrik 2018-10-14 18:25:37 UTC
+1 on this bug.

My GNOME sessions started crashing reproducibly 5 seconds after login.

The system logs show:

okt 14 20:09:37 nuc-local audit[809]: AVC avc:  denied  { write } for  pid=809 comm="dbus-broker" path="/run/boltd/power/2.guard.fifo" dev="tmpfs" ino=47520 scontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:boltd_var_run_t:s0 tclass=fifo_file permissive=0
okt 14 20:09:37 nuc-local dbus-broker-launch[808]: ERROR socket_recvmsg @ ../src/dbus/socket.c +606: State not recoverable
okt 14 20:09:37 nuc-local dbus-broker-launch[808]:       connection_dispatch @ ../src/dbus/connection.c +208
okt 14 20:09:37 nuc-local dbus-broker-launch[808]:       peer_dispatch_connection @ ../src/bus/peer.c +38
okt 14 20:09:37 nuc-local dbus-broker-launch[808]:       peer_dispatch @ ../src/bus/peer.c +127
okt 14 20:09:37 nuc-local dbus-broker-launch[808]:       dispatch_context_dispatch @ ../src/util/dispatch.c +345
okt 14 20:09:37 nuc-local dbus-broker-launch[808]:       broker_run @ ../src/broker/broker.c +181

After disabling boltd with

systemctl mask boltd.service

the system is functional again.

Comment 2 Lukas Vrabec 2018-10-15 11:25:14 UTC

*** This bug has been marked as a duplicate of bug 1637676 ***