Bug 2189347

Summary: SELinux is preventing ModemManager from using the 'execmem' accesses on a process.
Product: [Fedora] Fedora Reporter: kevinleroy
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, kevinleroy, lvrabec, mmalik, nknazeko, omosnacek, pkoncity, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:cc05a8e954c212f834ad04b3e80b872022ce61e9091212242b3941ba56fbaa0d;VARIANT_ID=kde;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-04-25 09:22:02 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: os_info
none
File: description none

Description kevinleroy 2023-04-24 22:18:03 UTC
Description of problem:
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   **************************

Si vous pensez que ModemManager devrait être autorisé à accéder execmem sur les processus étiquetés modemmanager_t par défaut.
Then vous devriez rapporter ceci en tant qu'anomalie.
Vous pouvez générer un module de stratégie local pour autoriser cet accès.
Do
autoriser cet accès pour le moment en exécutant :
# 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                Inconnu [ process ]
Source                        ModemManager
Source Path                   ModemManager
Port                          <Inconnu>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-38.11-1.fc38.noarch
Local Policy RPM              selinux-policy-targeted-38.11-1.fc38.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.2.11-300.fc38.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Thu Apr 13 20:27:09 UTC 2023
                              x86_64
Alert Count                   4
First Seen                    2023-03-29 02:00:09 CEST
Last Seen                     2023-04-25 00:15:35 CEST
Local ID                      91ac0b85-2629-4d8f-9c1b-79eaea15eca5

Raw Audit Messages
type=AVC msg=audit(1682374535.644:122): avc:  denied  { execmem } for  pid=1428 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.11-1.fc38.noarch

Additional info:
reporter:       libreport-2.17.9
hashmarkername: setroubleshoot
reason:         SELinux is preventing ModemManager from using the 'execmem' accesses on a process.
package:        selinux-policy-targeted-38.11-1.fc38.noarch
kernel:         6.2.11-300.fc38.x86_64
type:           libreport
component:      selinux-policy
component:      selinux-policy

Comment 1 kevinleroy 2023-04-24 22:18:05 UTC
Created attachment 1959659 [details]
File: os_info

Comment 2 kevinleroy 2023-04-24 22:18:08 UTC
Created attachment 1959660 [details]
File: description

Comment 3 Zdenek Pytela 2023-04-25 09:22:02 UTC

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