Description of problem: SELinux is preventing gdb from 'read' accesses on the chr_file card1. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that gdb should be allowed read access on the card1 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:dri_device_t:s0 Target Objects card1 [ chr_file ] Source gdb Source Path gdb Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-34.21-1.fc35.noarch Local Policy RPM selinux-policy-targeted-34.21-1.fc35.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 5.14.7-300.fc35.x86_64 #1 SMP Wed Sep 22 14:52:56 UTC 2021 x86_64 x86_64 Alert Count 53 First Seen 2021-09-30 17:00:31 PDT Last Seen 2021-09-30 23:23:44 PDT Local ID 632e1696-3c06-453d-9649-d156d2eaa9e0 Raw Audit Messages type=AVC msg=audit(1633069424.630:425): avc: denied { read } for pid=8328 comm="gdb" name="card1" dev="devtmpfs" ino=630 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:dri_device_t:s0 tclass=chr_file permissive=0 Hash: gdb,abrt_t,dri_device_t,chr_file,read Version-Release number of selected component: selinux-policy-targeted-34.21-1.fc35.noarch Additional info: component: selinux-policy reporter: libreport-2.15.2 hashmarkername: setroubleshoot kernel: 5.14.9-300.fc35.x86_64 type: libreport Potential duplicate: bug 1896648
Similar problem has been detected: When system starts up and after user logs in hashmarkername: setroubleshoot kernel: 5.14.14-300.fc35.x86_64 package: selinux-policy-targeted-35.3-1.20211019git94970fc.fc35.noarch reason: SELinux is preventing gdb from 'read' accesses on the chr_file card0. type: libreport
*** This bug has been marked as a duplicate of bug 1896648 ***