Bug 2478314
| Summary: | SELinux is preventing (smartctl) from 'entrypoint' accesses on the file /usr/bin/smartctl. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mr. Beedell, Roke Julian Lockhart (RJLB) <8ru2u4gz> | ||||||
| Component: | selinux-policy | Assignee: | Zdenek Pytela <zpytela> | ||||||
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 44 | CC: | 8ru2u4gz, dwalsh, lvrabec, mmalik, omosnacek, pkoncity, vmojzis, zpytela | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | abrt_hash:6a7a2b004fb5df91f333ac405d7c7c10ee722df1810ef4748f2ad439ff44e19e;VARIANT_ID=kde; | ||||||||
| Fixed In Version: | Doc Type: | --- | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 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 2141643 [details]
File: os_info
Created attachment 2141644 [details]
File: description
I performed this due to what https://discussion.fedoraproject.org/t/after-subnautica-2-boot-looped-kwin-abrt-corrupted-my-os-installation-s-b-tree-fs/191627 describes, if at all relevant. |
Description of problem: `run0 smartctl --health /dev/nvme1n1p4` displayed no output (whereas `sudo` does). SELinux is preventing (smartctl) from 'entrypoint' accesses on the file /usr/bin/smartctl. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that (smartctl) should be allowed entrypoint access on the smartctl file 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 '(smartctl)' --raw | audit2allow -M my-smartctl # semodule -X 300 -i my-smartctl.pp Additional Information: Source Context unconfined_u:unconfined_r:unconfined_t:s0- s0:c0.c1023 Target Context system_u:object_r:fsadm_exec_t:s0 Target Objects /usr/bin/smartctl [ file ] Source (smartctl) Source Path (smartctl) Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages smartmontools-7.5-6.fc44.x86_64 SELinux Policy RPM selinux-policy-targeted-43.3-1.fc44.noarch Local Policy RPM selinux-policy-targeted-43.3-1.fc44.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.19.10-300.fc44.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Mar 25 18:23:49 UTC 2026 x86_64 Alert Count 1 First Seen 2026-05-17 18:46:17 UTC Last Seen 2026-05-17 18:46:17 UTC Local ID a64bae9e-4542-4743-902d-7cf05adc4f8d Raw Audit Messages type=AVC msg=audit(1779043577.134:344): avc: denied { entrypoint } for pid=19183 comm="(smartctl)" path="/usr/bin/smartctl" dev="overlay" ino=12275275 scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=system_u:object_r:fsadm_exec_t:s0 tclass=file permissive=0 Hash: (smartctl),unconfined_t,fsadm_exec_t,file,entrypoint Version-Release number of selected component: selinux-policy-targeted-43.3-1.fc44.noarch Additional info: reporter: libreport-2.17.15 comment: `run0 smartctl --health /dev/nvme1n1p4` displayed no output (whereas `sudo` does). event_log: 2026-05-17-18:46:41> Looking for similar problems in bugzilla kernel: 6.19.10-300.fc44.x86_64 type: libreport hashmarkername: setroubleshoot component: selinux-policy package: selinux-policy-targeted-43.3-1.fc44.noarch reason: SELinux is preventing (smartctl) from 'entrypoint' accesses on the file /usr/bin/smartctl. component: selinux-policy