Bug 2089170 - SELinux is preventing systemctl from 'map' accesses on the file /usr/bin/systemctl.
Summary: SELinux is preventing systemctl from 'map' accesses on the file /usr/bin/syst...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 36
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:35ec2ee213472c0c74ab42325f3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-23 07:27 UTC by Kamil Páral
Modified: 2022-08-03 15:33 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-03 15:33:25 UTC
Type: ---


Attachments (Terms of Use)

Description Kamil Páral 2022-05-23 07:27:16 UTC
Description of problem:
I upgraded my F36 Workstation and rebooted. This is the first time I see this error, so it must be related to the recent update.
SELinux is preventing systemctl from 'map' accesses on the file /usr/bin/systemctl.

*****  Plugin catchall_boolean (89.3 confidence) suggests   ******************

If you want to allow domain to can mmap files
Then you must tell SELinux about this by enabling the 'domain_can_mmap_files' boolean.

Do
setsebool -P domain_can_mmap_files 1

*****  Plugin catchall (11.6 confidence) suggests   **************************

If you believe that systemctl should be allowed map access on the systemctl 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 'systemctl' --raw | audit2allow -M my-systemctl
# semodule -X 300 -i my-systemctl.pp

Additional Information:
Source Context                system_u:system_r:NetworkManager_dispatcher_custom
                              _t:s0
Target Context                system_u:object_r:systemd_systemctl_exec_t:s0
Target Objects                /usr/bin/systemctl [ file ]
Source                        systemctl
Source Path                   systemctl
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           systemd-250.3-8.fc36.x86_64
SELinux Policy RPM            selinux-policy-targeted-36.9-1.fc36.noarch
Local Policy RPM              selinux-policy-targeted-36.9-1.fc36.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 5.17.9-300.fc36.x86_64 #1 SMP
                              PREEMPT Wed May 18 15:08:23 UTC 2022 x86_64 x86_64
Alert Count                   1
First Seen                    2022-05-23 09:25:13 CEST
Last Seen                     2022-05-23 09:25:13 CEST
Local ID                      d1ea1ee1-40d8-4fe9-8f2e-3910cf3c51ac

Raw Audit Messages
type=AVC msg=audit(1653290713.727:248): avc:  denied  { map } for  pid=1396 comm="systemctl" path="/usr/bin/systemctl" dev="dm-0" ino=1836519 scontext=system_u:system_r:NetworkManager_dispatcher_custom_t:s0 tcontext=system_u:object_r:systemd_systemctl_exec_t:s0 tclass=file permissive=1


Hash: systemctl,NetworkManager_dispatcher_custom_t,systemd_systemctl_exec_t,file,map

Version-Release number of selected component:
selinux-policy-targeted-36.9-1.fc36.noarch

Additional info:
component:      selinux-policy
reporter:       libreport-2.17.1
hashmarkername: setroubleshoot
kernel:         5.17.9-300.fc36.x86_64
type:           libreport

Comment 1 Zdenek Pytela 2022-05-23 11:15:13 UTC
Kamile,

Do you know which script triggers this denial?

Comment 2 Kamil Páral 2022-05-23 11:43:01 UTC
See bug 2089171 comment 4

Comment 3 Johannes Kalliauer 2022-05-28 11:11:38 UTC
Similar problem has been detected:

used airport-wifi

hashmarkername: setroubleshoot
kernel:         5.17.11-300.fc36.x86_64
package:        selinux-policy-targeted-36.9-1.fc36.noarch
reason:         SELinux is preventing systemctl from 'map' accesses on the file /usr/bin/systemctl.
type:           libreport

Comment 4 Johannes Kalliauer 2022-05-29 10:29:12 UTC
Similar problem has been detected:

in the USA I switched to the University-VPN in Europe

hashmarkername: setroubleshoot
kernel:         5.17.11-300.fc36.x86_64
package:        selinux-policy-targeted-36.9-1.fc36.noarch
reason:         SELinux is preventing systemctl from 'map' accesses on the file /usr/bin/systemctl.
type:           libreport

Comment 5 Davide Repetto 2022-05-29 18:07:01 UTC
Similar problem has been detected:

This happens at boot, even after "fixfiles onboot", together with another 10 AVCs.


hashmarkername: setroubleshoot
kernel:         5.17.11-300.fc36.x86_64
package:        selinux-policy-targeted-36.9-1.fc36.noarch
reason:         SELinux is preventing systemctl from 'map' accesses on the file /usr/bin/systemctl.
type:           libreport

Comment 6 Zdenek Pytela 2022-08-03 15:33:25 UTC
I believe this AVC has been addressed in the latest release:

# sesearch -A -s NetworkManager_dispatcher_custom_t -t systemd_systemctl_exec_t -c file -p execute
allow NetworkManager_dispatcher_custom_t systemd_systemctl_exec_t:file { execute execute_no_trans getattr ioctl lock map open read };
# rpm -q selinux-policy
selinux-policy-36.10-1.fc36.noarch


Note You need to log in before you can comment on or make changes to this bug.