Bug 2223751
| Summary: | SELinux is preventing gdb from 'read' accesses on the chr_file nvidia0. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | James <threedeemania> | ||||||
| Component: | selinux-policy | Assignee: | Zdenek Pytela <zpytela> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 38 | CC: | dwalsh, lvrabec, mmalik, nknazeko, omosnacek, pkoncity, threedeemania, vmojzis, zpytela | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:cfd909b08f7249b9181382e2dc9b9f777920f5a509ffe0330d9c96cf2788c4df;VARIANT_ID=kde; | ||||||||
| Fixed In Version: | selinux-policy-38.21-1.fc39.noarch selinux-policy-38.21-1.fc38.noarch | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2023-07-18 19:14: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 1976373 [details]
File: description
Created attachment 1976374 [details]
File: os_info
|
Description of problem: SELinux is preventing gdb from 'read' accesses on the chr_file nvidia0. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that gdb should be allowed read access on the nvidia0 chr_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 'gdb' --raw | audit2allow -M my-gdb # semodule -X 300 -i my-gdb.pp Additional Information: Source Context system_u:system_r:abrt_t:s0-s0:c0.c1023 Target Context system_u:object_r:xserver_misc_device_t:s0 Target Objects nvidia0 [ chr_file ] Source gdb Source Path gdb Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-38.20-1.fc38.noarch Local Policy RPM selinux-policy-targeted-38.20-1.fc38.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.3.12-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jul 6 04:05:18 UTC 2023 x86_64 Alert Count 4 First Seen 2023-07-16 18:11:14 EDT Last Seen 2023-07-17 20:09:19 EDT Local ID c7510a1c-f4a4-45c7-990f-9ef4bce059dc Raw Audit Messages type=AVC msg=audit(1689638959.275:471): avc: denied { read } for pid=46797 comm="gdb" name="nvidia0" dev="devtmpfs" ino=755 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xserver_misc_device_t:s0 tclass=chr_file permissive=0 Hash: gdb,abrt_t,xserver_misc_device_t,chr_file,read Version-Release number of selected component: selinux-policy-targeted-38.20-1.fc38.noarch Additional info: reporter: libreport-2.17.11 reason: SELinux is preventing gdb from 'read' accesses on the chr_file nvidia0. package: selinux-policy-targeted-38.20-1.fc38.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport kernel: 6.3.12-200.fc38.x86_64 component: selinux-policy