Description of problem: SELinux is preventing abrtd from map_read, map_write access on the bpf labeled init_t. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that abrtd should be allowed map_read map_write access on bpf 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 'abrtd' --raw | audit2allow -M my-abrtd # semodule -X 300 -i my-abrtd.pp Additional Information: Source Context system_u:system_r:abrt_t:s0-s0:c0.c1023 Target Context system_u:system_r:init_t:s0 Target Objects Unknown [ bpf ] Source abrtd Source Path abrtd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-40.5-1.fc40.noarch Local Policy RPM selinux-policy-targeted-40.5-1.fc40.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 6.7.0-0.rc2.22.fc40.x86_64+debug #1 SMP PREEMPT_DYNAMIC Mon Nov 20 14:05:16 UTC 2023 x86_64 Alert Count 2 First Seen 2023-11-22 03:21:09 +05 Last Seen 2023-11-22 03:21:46 +05 Local ID 5e877575-9736-4605-83bb-216e9de42a2b Raw Audit Messages type=AVC msg=audit(1700605306.309:236): avc: denied { map_read map_write } for pid=9717 comm="abrt-dbus" scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:system_r:init_t:s0 tclass=bpf permissive=1 Hash: abrtd,abrt_t,init_t,bpf,map_read,map_write Version-Release number of selected component: selinux-policy-targeted-40.5-1.fc40.noarch Additional info: reporter: libreport-2.17.11 reason: SELinux is preventing abrtd from map_read, map_write access on the bpf labeled init_t. package: selinux-policy-targeted-40.5-1.fc40.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport kernel: 6.7.0-0.rc2.22.fc40.x86_64+debug component: selinux-policy
Created attachment 2000784 [details] File: description
Created attachment 2000785 [details] File: os_info
*** This bug has been marked as a duplicate of bug 2250930 ***