Bug 2203332
| Summary: | SELinux is preventing systemd from using the 'setcurrent' accesses on a process. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| 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, lvrabec, mikhail.v.gavrilov, mmalik, nknazeko, omosnacek, pkoncity, vmojzis, zpytela | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:cae9108fc73d43937cd466d1b7b6bb3e27bd6f2fa516d732ab89f0d7df9212ad;VARIANT_ID=workstation; | ||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2023-05-15 09:55:27 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 1964117 [details]
File: description
Created attachment 1964118 [details]
File: os_info
Demonstration: https://youtu.be/mbox4DWVEIs *** This bug has been marked as a duplicate of bug 2186821 *** |
Description of problem: happens while glibc, kernel and mesa update SELinux is preventing systemd from using the 'setcurrent' accesses on a process. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemd should be allowed setcurrent access on processes labeled init_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 'systemd' --raw | audit2allow -M my-systemd # semodule -X 300 -i my-systemd.pp Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:system_r:init_t:s0 Target Objects Unknown [ process ] Source systemd Source Path systemd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-38.12-1.fc39.noarch Local Policy RPM selinux-policy-targeted-38.12-1.fc39.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 6.4.0- 0.rc1.20230510git16a8829130ca.18.fc39.x86_64+debug #1 SMP PREEMPT_DYNAMIC Wed May 10 17:34:20 UTC 2023 x86_64 Alert Count 2 First Seen 2023-05-12 04:38:11 +05 Last Seen 2023-05-12 04:39:08 +05 Local ID 504f3e4e-7bd8-4f4c-a8b7-cd993fdfaf14 Raw Audit Messages type=AVC msg=audit(1683848348.318:790): avc: denied { setcurrent } for pid=1 comm="systemd" scontext=system_u:system_r:init_t:s0 tcontext=system_u:system_r:init_t:s0 tclass=process permissive=1 Hash: systemd,init_t,init_t,process,setcurrent Version-Release number of selected component: selinux-policy-targeted-38.12-1.fc39.noarch Additional info: reporter: libreport-2.17.9 reason: SELinux is preventing systemd from using the 'setcurrent' accesses on a process. package: selinux-policy-targeted-38.12-1.fc39.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport kernel: 6.4.0-0.rc1.20230510git16a8829130ca.18.fc39.x86_64+debug comment: happens while glibc, kernel and mesa update component: selinux-policy