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.

Bug 2057147

Summary: NetworkManager produces SElinux AVC on every network change (virsh/vpn etc.)
Product: Red Hat Enterprise Linux 8 Reporter: Leon Fauster <leonfauster>
Component: NetworkManagerAssignee: NetworkManager Development Team <nm-team>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bgalvani, bstinson, jwboyer, lrintel, rkhan, sukulkar, thaller, till
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-23 15:34:55 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 Leon Fauster 2022-02-22 19:26:14 UTC
NetworkManager produces SElinux AVC on every network change (virsh/vpn etc.)

Description of problem:

# rpm -qf /usr/libexec/nm-dispatcher
NetworkManager-1.36.0-0.7.el8.x86_64


journal:

setroubleshoot[26075]: SELinux is preventing /usr/libexec/nm-dispatcher from execute access on the file 04-iscsi. For complete SELinux messages run: sealert -l c55469ca-64b2-409d-ae58-5a5b0e00aa6a


ausearch:

time->Tue Feb 22 20:18:29 2022
type=PROCTITLE msg=audit(1645557509.725:332): proctitle="/usr/libexec/nm-dispatcher"
type=SYSCALL msg=audit(1645557509.725:332): arch=c000003e syscall=59 success=no exit=-13 a0=5562ded58fc0 a1=7ffe1691e5c0 a2=5562ded5e660 a3=0 items=0 ppid=26068 pid=26073 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="nm-dispatcher" exe="/usr/libexec/nm-dispatcher" subj=system_u:system_r:NetworkManager_dispatcher_t:s0 key=(null)
type=AVC msg=audit(1645557509.725:332): avc:  denied  { execute } for  pid=26073 comm="nm-dispatcher" name="04-iscsi" dev="dm-1" ino=3148449 scontext=system_u:system_r:NetworkManager_dispatcher_t:s0 tcontext=system_u:object_r:NetworkManager_dispatcher_script_t:s0 tclass=file permissive=0



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

# rpm -q selinux-policy-targeted NetworkManager
selinux-policy-targeted-3.14.3-91.el8.noarch
NetworkManager-1.36.0-0.7.el8.x86_64

Comment 1 Till Maas 2022-02-23 15:18:15 UTC
Thomas, please take a look and re-assign it if necessary.

Comment 2 Till Maas 2022-02-23 15:34:55 UTC

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