Bug 2229020

Summary: SELinux is preventing ModemManager from using the 'execmem' accesses on a process.
Product: [Fedora] Fedora Reporter: Sandro <gui1ty>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: dwalsh, gui1ty, lvrabec, mmalik, nknazeko, omosnacek, pkoncity, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:cc05a8e954c212f834ad04b3e80b872022ce61e9091212242b3941ba56fbaa0d;VARIANT_ID=;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-04 19:30:23 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:
Attachments:
Description Flags
File: description
none
File: os_info none

Description Sandro 2023-08-03 23:53:18 UTC
Description of problem:
It happens on every boot.
SELinux is preventing ModemManager from using the 'execmem' accesses on a process.

*****  Plugin allow_execmem (91.4 confidence) suggests   *********************

If this issue occurred during normal system operation.
Then this alert could be a serious issue and your system could be compromised.
Do
contact your security administrator and report this issue

*****  Plugin catchall (9.59 confidence) suggests   **************************

If you believe that ModemManager should be allowed execmem access on processes labeled modemmanager_t 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 'ModemManager' --raw | audit2allow -M my-ModemManager
# semodule -X 300 -i my-ModemManager.pp

Additional Information:
Source Context                system_u:system_r:modemmanager_t:s0
Target Context                system_u:system_r:modemmanager_t:s0
Target Objects                Unknown [ process ]
Source                        ModemManager
Source Path                   ModemManager
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-38.22-1.fc38.noarch
Local Policy RPM              selinux-policy-targeted-38.22-1.fc38.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.4.7-200.fc38.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Thu Jul 27 20:01:18 UTC 2023
                              x86_64
Alert Count                   1
First Seen                    2023-08-03 23:50:53 GMT
Last Seen                     2023-08-03 23:50:53 GMT
Local ID                      5c502aeb-5043-4111-b002-c1841990b24f

Raw Audit Messages
type=AVC msg=audit(1691106653.548:120): avc:  denied  { execmem } for  pid=1197 comm="ModemManager" scontext=system_u:system_r:modemmanager_t:s0 tcontext=system_u:system_r:modemmanager_t:s0 tclass=process permissive=0


Hash: ModemManager,modemmanager_t,modemmanager_t,process,execmem

Version-Release number of selected component:
selinux-policy-targeted-38.22-1.fc38.noarch

Additional info:
reporter:       libreport-2.17.11
reason:         SELinux is preventing ModemManager from using the 'execmem' accesses on a process.
package:        selinux-policy-targeted-38.22-1.fc38.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.4.7-200.fc38.x86_64
comment:        It happens on every boot.
component:      selinux-policy

Comment 1 Sandro 2023-08-03 23:53:21 UTC
Created attachment 1981549 [details]
File: description

Comment 2 Sandro 2023-08-03 23:53:23 UTC
Created attachment 1981550 [details]
File: os_info

Comment 3 Zdenek Pytela 2023-08-04 19:30:23 UTC

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