Bug 2156070

Summary: SELinux is preventing /usr/sbin/wpa_supplicant from using the 'bpf' capabilities
Product: Red Hat Enterprise Linux 9 Reporter: Lalit Dhiri <lalit_dhiri>
Component: wpa_supplicantAssignee: Davide Caratti <dcaratti>
Status: CLOSED MIGRATED QA Contact: Laura Trivelloni <ltrivell>
Severity: low Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bstinson, jwboyer, sukulkar
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-21 12:28:49 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 Lalit Dhiri 2022-12-23 16:59:06 UTC
Description of problem:

SELinux is preventing /usr/sbin/wpa_supplicant from using the 'bpf' capabilities.

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

If you believe that wpa_supplicant should have the bpf capability 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 'wpa_supplicant' --raw | audit2allow -M my-wpasupplicant
# semodule -X 300 -i my-wpasupplicant.pp

Additional Information:
Source Context                system_u:system_r:NetworkManager_t:s0
Target Context                system_u:system_r:NetworkManager_t:s0
Target Objects                Unknown [ capability2 ]
Source                        wpa_supplicant
Source Path                   /usr/sbin/wpa_supplicant
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           wpa_supplicant-2.10-4.el9.x86_64
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-38.1.3-1.el9.noarch
Local Policy RPM              selinux-policy-targeted-38.1.3-1.el9.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 5.14.0-214.el9.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Thu Dec 15 01:34:46 UTC 2022
                              x86_64 x86_64
Alert Count                   33
First Seen                    2022-12-23 01:36:20 GMT
Last Seen                     2022-12-23 16:47:42 GMT
Local ID                      111cf57e-1666-446e-acd5-2198fa72a30d

Raw Audit Messages
type=AVC msg=audit(1671814062.695:340): avc:  denied  { bpf } for  pid=1349 comm="wpa_supplicant" capability=39  scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:system_r:NetworkManager_t:s0 tclass=capability2 permissive=0


type=SYSCALL msg=audit(1671814062.695:340): arch=x86_64 syscall=setsockopt success=yes exit=0 a0=c a1=1 a2=1a a3=56486cd453a0 items=0 ppid=1 pid=1349 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=wpa_supplicant exe=/usr/sbin/wpa_supplicant subj=system_u:system_r:NetworkManager_t:s0 key=(null)

Hash: wpa_supplicant,NetworkManager_t,NetworkManager_t,capability2,bpf



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


How reproducible:

Keeps cropping up after login to CentOS Stream 9

Comment 1 RHEL Program Management 2023-09-21 12:26:01 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-21 12:28:49 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.