Bug 2185431

Summary: SELinux is preventing stress-ng-close from 'setattr' accesses on the anon_inode [userfaultfd].
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: dwalsh, lvrabec, mikhail.v.gavrilov, mmalik, omosnacek, pkoncity, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f90d3e4e15492a390e21808d361b41692a71c2ee0d6fe18ffcad5cea2e84c765;VARIANT_ID=workstation;
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:
Description Flags
File: description
none
File: os_info none

Description Mikhail 2023-04-09 09:18:01 UTC
Description of problem:
Launch stress-ng with follow parameters
 $ stress-ng --all 8  --timeout 60s --metrics-brief --tz
SELinux is preventing stress-ng-close from 'setattr' accesses on the anon_inode [userfaultfd].

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that stress-ng-close should be allowed setattr access on the [userfaultfd] anon_inode 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 'stress-ng-close' --raw | audit2allow -M my-stressngclose
# semodule -X 300 -i my-stressngclose.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:unconfined_t:s0-
                              s0:c0.c1023
Target Context                unconfined_u:object_r:unconfined_t:s0
Target Objects                [userfaultfd] [ anon_inode ]
Source                        stress-ng-close
Source Path                   stress-ng-close
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-38.10-1.fc39.noarch
Local Policy RPM              selinux-policy-targeted-38.10-1.fc39.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 6.3.0-
                              0.rc5.20230407gitf2afccfefe7b.46.fc39.x86_64+debug
                              #1 SMP PREEMPT_DYNAMIC Fri Apr 7 16:08:59 UTC 2023
                              x86_64
Alert Count                   6
First Seen                    2023-04-09 14:08:10 +05
Last Seen                     2023-04-09 14:14:53 +05
Local ID                      853ca782-afe8-43d5-9a32-1862d413c6ad

Raw Audit Messages
type=AVC msg=audit(1681031693.315:1698): avc:  denied  { setattr } for  pid=26433 comm="stress-ng-close" name="[userfaultfd]" dev="anon_inodefs" ino=328148 scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:unconfined_t:s0 tclass=anon_inode permissive=1


Hash: stress-ng-close,unconfined_t,unconfined_t,anon_inode,setattr

Version-Release number of selected component:
selinux-policy-targeted-38.10-1.fc39.noarch

Additional info:
reporter:       libreport-2.17.9
reason:         SELinux is preventing stress-ng-close from 'setattr' accesses on the anon_inode [userfaultfd].
package:        selinux-policy-targeted-38.10-1.fc39.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.3.0-0.rc5.20230407gitf2afccfefe7b.46.fc39.x86_64+debug
component:      selinux-policy

Comment 1 Mikhail 2023-04-09 09:18:04 UTC
Created attachment 1956428 [details]
File: description

Comment 2 Mikhail 2023-04-09 09:18:06 UTC
Created attachment 1956429 [details]
File: os_info

Comment 3 Fedora Release Engineering 2023-08-16 07:13:12 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.