Bug 2548363
| Summary: | SELinux is preventing /usr/lib/systemd/systemd-userwork from 'read' accesses on the sock_file io.systemd.NamespaceResource. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bill <thetaeridanus> | ||||||
| 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: | 45 | CC: | dwalsh, lvrabec, mmalik, omosnacek, pkoncity, thetaeridanus, vmojzis, zpytela | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:4e451586d1f02eb70a561d8bc82961d5ee5d086ed49d33afda44a2c60ba28b0d;VARIANT_ID=workstation; | ||||||||
| Fixed In Version: | Doc Type: | --- | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2026-10-09 08:38:48 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 2160491 [details]
File: description
Created attachment 2160492 [details]
File: os_info
*** This bug has been marked as a duplicate of bug 2541947 *** |
Description of problem: Immediately after upgrade to fedora 45 SELinux is preventing /usr/lib/systemd/systemd-userwork from 'read' accesses on the sock_file io.systemd.NamespaceResource. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemd-userwork should be allowed read access on the io.systemd.NamespaceResource sock_file by default. Then You should report this as a bug. If you are certain this access is legitimate and not an intrusion attempt, you can generate a local policy module to allow it. Custom policy modules are not supported as they may weaken the system policy and expose the system to security vulnerabilities. Do # ausearch -c 'systemd-userwor' --raw | audit2allow -M my-systemduserwor # semodule -X 300 -i my-systemduserwor.pp Additional Information: Source Context system_u:system_r:systemd_userdbd_t:s0 Target Context system_u:object_r:systemd_nsresourced_runtime_t:s0 Target Objects io.systemd.NamespaceResource [ sock_file ] Source systemd-userwor Source Path /usr/lib/systemd/systemd-userwork Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-45.20-1.fc45.noarch Local Policy RPM selinux-policy-targeted-45.20-1.fc45.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 7.2.9-300.fc45.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Oct 3 16:19:58 UTC 2026 x86_64 Alert Count 151 First Seen 2026-10-09 17:36:21 NZDT Last Seen 2026-10-09 17:59:18 NZDT Local ID 9bd6762d-463e-4000-9cdf-216182cf583c Raw Audit Messages type=AVC msg=audit(1791521958.658:778): avc: denied { read } for pid=5416 comm="systemd-userwor" name="io.systemd.NamespaceResource" dev="tmpfs" ino=1148 scontext=system_u:system_r:systemd_userdbd_t:s0 tcontext=system_u:object_r:systemd_nsresourced_runtime_t:s0 tclass=sock_file permissive=0 Hash: systemd-userwor,systemd_userdbd_t,systemd_nsresourced_runtime_t,sock_file,read Version-Release number of selected component: selinux-policy-targeted-45.20-1.fc45.noarch Additional info: reporter: libreport-2.17.15 reason: SELinux is preventing /usr/lib/systemd/systemd-userwork from 'read' accesses on the sock_file io.systemd.NamespaceResource. package: selinux-policy-targeted-45.20-1.fc45.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport kernel: 7.2.9-300.fc45.x86_64 comment: Immediately after upgrade to fedora 45 component: selinux-policy