Bug 2272027

Summary: SELinux is preventing systemd-coredum from using the 'sys_admin' capabilities.
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 40CC: dwalsh, knazekovan, kparal, lvrabec, mmalik, omosnacek, pkoncity, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:3f3c41747902206a7bd50598ec7bf5dcf9adec13d24f9578c4d6f532f6ac1b6c;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-09 11:10:26 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 Kamil Páral 2024-03-28 09:11:57 UTC
Description of problem:
Started happening after upgrade to F40. I think this is related to a Steam crash, and abrt trying to act on it?
SELinux is preventing systemd-coredum from using the 'sys_admin' capabilities.

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

If you believe that systemd-coredum should have the sys_admin 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 'systemd-coredum' --raw | audit2allow -M my-systemdcoredum
# semodule -X 300 -i my-systemdcoredum.pp

Additional Information:
Source Context                system_u:system_r:systemd_coredump_t:s0
Target Context                system_u:system_r:systemd_coredump_t:s0
Target Objects                Unknown [ capability ]
Source                        systemd-coredum
Source Path                   systemd-coredum
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-40.15-1.fc40.noarch
Local Policy RPM              selinux-policy-targeted-40.15-1.fc40.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.8.1-300.fc40.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Wed Mar 20 04:39:30 UTC 2024
                              x86_64
Alert Count                   1
First Seen                    2024-03-28 09:52:34 CET
Last Seen                     2024-03-28 09:52:34 CET
Local ID                      6e8f4f2d-318c-48cd-88fe-84e0d539ffd5

Raw Audit Messages
type=AVC msg=audit(1711615954.113:473): avc:  denied  { sys_admin } for  pid=20838 comm="systemd-coredum" capability=21  scontext=system_u:system_r:systemd_coredump_t:s0 tcontext=system_u:system_r:systemd_coredump_t:s0 tclass=capability permissive=0


Hash: systemd-coredum,systemd_coredump_t,systemd_coredump_t,capability,sys_admin

Version-Release number of selected component:
selinux-policy-targeted-40.15-1.fc40.noarch

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing systemd-coredum from using the 'sys_admin' capabilities.
package:        selinux-policy-targeted-40.15-1.fc40.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.8.1-300.fc40.x86_64
comment:        Started happening after upgrade to F40. I think this is related to a Steam crash, and abrt trying to act on it?
component:      selinux-policy

Comment 1 Kamil Páral 2024-03-28 09:11:59 UTC
Created attachment 2023974 [details]
File: description

Comment 2 Kamil Páral 2024-03-28 09:12:01 UTC
Created attachment 2023975 [details]
File: os_info

Comment 3 Zdenek Pytela 2024-05-02 12:43:31 UTC
Kamile,

If this issue is still in place, do you know how to reproduce it?
We need some additional information, with full auditing if possible.
https://fedoraproject.org/wiki/SELinux/Debugging#Enable_full_auditing

Note systemd-coredump is different to abrt.

Comment 4 Kamil Páral 2024-05-02 13:07:53 UTC
Hi, I haven't seen this error in a long time, and can't reproduce it at this moment.

Comment 5 Zdenek Pytela 2024-05-09 11:10:26 UTC

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