Bug 1934756
| Summary: | SELinux is preventing systemd-coredum from using the 'fowner' capabilities. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> |
| 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: | rawhide | CC: | dwalsh, grepl.miroslav, lvrabec, mmalik, omosnace, patrick, plautrba, vmojzis, zpytela |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:5b2d03d9fd559d18df058be012c8809527024adb2faa19de709c39b51791376b;VARIANT_ID=workstation; | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-03-23 17:05:24 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: | |||
Similar problem has been detected: 1. Launch Calendar application 2. Close Calendar application 3. Launch Calendar application again (here happened crash and this SELinux alert) hashmarkername: setroubleshoot kernel: 5.12.0-0.rc2.165.fc35.x86_64+debug package: selinux-policy-targeted-3.14.8-4.fc35.noarch reason: SELinux is preventing systemd-coredum from using the 'fowner' capabilities. type: libreport *** Bug 1938387 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 1933437 *** |
Description of problem: SELinux is preventing systemd-coredum from using the 'fowner' capabilities. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemd-coredum should have the fowner 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-3.14.8-4.fc35.noarch Local Policy RPM selinux-policy-targeted-3.14.8-4.fc35.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 5.12.0-0.rc1.162.fc35.x86_64+debug #1 SMP Tue Mar 2 01:11:26 +05 2021 x86_64 x86_64 Alert Count 1 First Seen 2021-03-03 23:44:37 +05 Last Seen 2021-03-03 23:44:37 +05 Local ID 0d3490da-ee0a-408b-906c-6b54bf44179c Raw Audit Messages type=AVC msg=audit(1614797077.235:597): avc: denied { fowner } for pid=5552 comm="systemd-coredum" capability=3 scontext=system_u:system_r:systemd_coredump_t:s0 tcontext=system_u:system_r:systemd_coredump_t:s0 tclass=capability permissive=1 Hash: systemd-coredum,systemd_coredump_t,systemd_coredump_t,capability,fowner Version-Release number of selected component: selinux-policy-targeted-3.14.8-4.fc35.noarch Additional info: component: selinux-policy reporter: libreport-2.14.0 hashmarkername: setroubleshoot kernel: 5.12.0-0.rc1.162.fc35.x86_64+debug type: libreport