Bug 1598506

Summary: SELinux prevents NetworkManager from mmap()-ing /usr/sbin/dnsmasq
Product: Red Hat Enterprise Linux 7 Reporter: Martin Pitt <mpitt>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: lvrabec, mgrepl, mmalik, plautrba, ssekidde
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 10:06:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Pitt 2018-07-05 16:07:33 UTC
Description of problem: When NetworkManager runs dnsmasq on current RHEL 7.6 nightlies, the following SELinux error appears:

type=1400 audit(1530806620.255:4): avc:  denied  { map } for  pid=2269 comm="dnsmasq" path="/usr/sbin/dnsmasq" dev="dm-0" ino=714988 scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:object_r:dnsmasq_exec_t:s0 tclass=file permissive=0

Version-Release number of selected component (if applicable):


How reproducible: Always (with Cockpit's check-networking-settings integration test)


Additional info: This has never been seen on any other operating system (Fedora 27/28, RHEL 7.5, CentOS 7, RHEL 8, etc.), it happens *only* on RHEL 7.6.

Comment 2 Martin Pitt 2018-07-05 16:08:50 UTC
Whoops, forgot the package versions:

selinux-policy-targeted-3.13.1-207.el7.noarch
selinux-policy-3.13.1-207.el7.noarch
NetworkManager-1.12.0-1.el7.x86_64
dnsmasq-2.76-7.el7.x86_64
libselinux-2.5-13.el7.x86_64

Comment 3 Lukas Vrabec 2018-07-20 10:27:15 UTC

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

Comment 6 errata-xmlrpc 2018-10-30 10:06:08 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://access.redhat.com/errata/RHBA-2018:3111