Bug 2335669
| Summary: | SELinux is preventing /usr/lib/systemd/systemd-coredump from using the 'sys_admin' capabilities. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Franco Profeti <fprofeti98> | ||||||
| Component: | selinux-policy | Assignee: | Zdenek Pytela <zpytela> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 41 | CC: | dwalsh, fprofeti98, 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: | 2025-01-21 11:53:36 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: |
|
||||||||
Created attachment 2064739 [details]
File: os_info
Created attachment 2064740 [details]
File: description
*** This bug has been marked as a duplicate of bug 2335200 *** |
Description of problem: I turn on my computer, on GDM I shut down without login in. Then turn on, login in into my account using a gnome x11 session, used Firefox for a bit, and this happened. Maybe unrelated to my steps, pretty random. SELinux is preventing /usr/lib/systemd/systemd-coredump from using the 'sys_admin' capabilities. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemd-coredump 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 /usr/lib/systemd/systemd-coredump Port <Unknown> Host (removed) Source RPM Packages systemd-udev-256.10-1.fc41.x86_64 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 1 First Seen 2025-01-04 23:07:48 -03 Last Seen 2025-01-04 23:07:48 -03 Local ID a2348f66-1762-4512-853f-39d9eaa88f9e Raw Audit Messages type=AVC msg=audit(1736042868.640:1002): avc: denied { sys_admin } for pid=35302 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 type=SYSCALL msg=audit(1736042868.640:1002): arch=x86_64 syscall=lgetxattr success=no exit=ENODATA a0=55a3625bb500 a1=7f1c8bb46117 a2=55a3625c5b30 a3=67 items=0 ppid=2 pid=35302 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=systemd-coredum exe=/usr/lib/systemd/systemd-coredump subj=system_u:system_r:systemd_coredump_t:s0 key=(null) 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 package: selinux-policy-targeted-41.27-1.fc41.noarch type: libreport reason: SELinux is preventing /usr/lib/systemd/systemd-coredump from using the 'sys_admin' capabilities. comment: I turn on my computer, on GDM I shut down without login in. Then turn on, login in into my account using a gnome x11 session, used Firefox for a bit, and this happened. Maybe unrelated to my steps, pretty random. hashmarkername: setroubleshoot component: selinux-policy kernel: 6.12.7-200.fc41.x86_64 component: selinux-policy