Bug 2228421 - SELinux is preventing ModemManager from using the 'execmem' accesses on a process.
Summary: SELinux is preventing ModemManager from using the 'execmem' accesses on a pro...
Keywords:
Status: CLOSED DUPLICATE of bug 2228059
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 38
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:cc05a8e954c212f834ad04b3e80...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-02 11:18 UTC by dani
Modified: 2023-08-02 11:23 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-02 11:23:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: description (2.19 KB, text/plain)
2023-08-02 11:18 UTC, dani
no flags Details
File: os_info (698 bytes, text/plain)
2023-08-02 11:18 UTC, dani
no flags Details

Description dani 2023-08-02 11:18:21 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   **************************

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.6-200.fc38.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Mon Jul 24 20:51:12 UTC 2023
                              x86_64
Alert Count                   120
First Seen                    2022-12-16 20:19:39 IST
Last Seen                     2023-08-02 14:12:17 IDT
Local ID                      c80e5595-753e-46b9-8959-234877b6c9ea

Raw Audit Messages
type=AVC msg=audit(1690974737.697:124): avc:  denied  { execmem } for  pid=1087 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.6-200.fc38.x86_64
component:      selinux-policy

Comment 1 dani 2023-08-02 11:18:24 UTC
Created attachment 1981299 [details]
File: description

Comment 2 dani 2023-08-02 11:18:26 UTC
Created attachment 1981300 [details]
File: os_info

Comment 3 Zdenek Pytela 2023-08-02 11:23:37 UTC

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


Note You need to log in before you can comment on or make changes to this bug.