Bug 2334966

Summary: SELinux is preventing systemd-coredum from using the 'sys_admin' capabilities.
Product: [Fedora] Fedora Reporter: Fabio Valentini <decathorpe>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 41CC: decathorpe, dwalsh, lvrabec, mmalik, omosnacek, pkoncity, sourcefan.sb29n, 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: 2025-01-21 11:54:59 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 Fabio Valentini 2024-12-30 18:14:24 UTC
Description of problem:
This appears to happen every time systemd-coredumpctl / ABRT attempt to process a crash report.
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-41.27-1.fc41.noarch
Local Policy RPM              selinux-policy-targeted-41.27-1.fc41.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.12.7-200.fc41.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Fri Dec 27 17:05:33 UTC 2024
                              x86_64
Alert Count                   3
First Seen                    2024-12-28 17:54:11 CET
Last Seen                     2024-12-30 14:04:19 CET
Local ID                      1a94a700-3b33-42f8-bd1c-fca20cb517e8

Raw Audit Messages
type=AVC msg=audit(1735563859.982:233): avc:  denied  { sys_admin } for  pid=8683 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-41.27-1.fc41.noarch

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing systemd-coredum from using the 'sys_admin' capabilities.
package:        selinux-policy-targeted-41.27-1.fc41.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.12.7-200.fc41.x86_64
comment:        This appears to happen every time systemd-coredumpctl / ABRT attempt to process a crash report.
component:      selinux-policy

Comment 1 Fabio Valentini 2024-12-30 18:14:27 UTC
Created attachment 2064301 [details]
File: description

Comment 2 Fabio Valentini 2024-12-30 18:14:28 UTC
Created attachment 2064302 [details]
File: os_info

Comment 3 Zdenek Pytela 2025-01-21 11:54:59 UTC

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