Description of problem: SELinux is preventing kworker/0:1 from map_read, map_write access on the bpf labeled kernel_t. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that 0:1 should be allowed map_read map_write access on bpf labeled kernel_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 'kworker/0:1' --raw | audit2allow -M my-kworker01 # semodule -X 300 -i my-kworker01.pp Additional Information: Source Context system_u:system_r:kernel_t:s0 Target Context system_u:system_r:kernel_t:s0 Target Objects Unknown [ bpf ] Source kworker/0:1 Source Path kworker/0:1 Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-38.12-1.fc38.noarch Local Policy RPM selinux-policy-targeted-38.12-1.fc38.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.3.3-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Wed May 17 14:31:24 UTC 2023 x86_64 Alert Count 2 First Seen 2023-05-19 17:57:40 CEST Last Seen 2023-05-19 17:57:40 CEST Local ID 78914553-fd24-44db-8b4c-54127cc22891 Raw Audit Messages type=AVC msg=audit(1684511860.893:1320): avc: denied { map_read map_write } for pid=514157 comm="kworker/0:1" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=bpf permissive=0 Hash: kworker/0:1,kernel_t,kernel_t,bpf,map_read,map_write Version-Release number of selected component: selinux-policy-targeted-38.12-1.fc38.noarch Additional info: reporter: libreport-2.17.10 type: libreport kernel: 6.3.3-200.fc38.x86_64 package: selinux-policy-targeted-38.12-1.fc38.noarch reason: SELinux is preventing kworker/0:1 from map_read, map_write access on the bpf labeled kernel_t. component: selinux-policy hashmarkername: setroubleshoot component: selinux-policy
Created attachment 1965740 [details] File: os_info
Created attachment 1965741 [details] File: description
*** This bug has been marked as a duplicate of bug 2186595 ***