Bug 2370706

Summary: SELinux is preventing rpc-virtqemud from 'getattr' accesses on the directory /dev/binderfs.
Product: [Fedora] Fedora Reporter: Mr. Beedell, Roke Julian Lockhart (RJLB) <8ru2u4gz>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 42CC: 8ru2u4gz, dwalsh, lvrabec, mmalik, omosnacek, pkoncity, vmojzis, zpytela
Target Milestone: ---Flags: 8ru2u4gz: needinfo? (zpytela)
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:9cb0c8113fd8c33f59497d3b9b06700e0f5a1cf9f7af95c6aba3a3ef6ecfb9a2;VARIANT_ID=kde;
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 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-06-06 13:07:25 UTC
Description of problem:
I created a VM with `neon-unstable-20250601-1146.iso`, whose type was `cpe:/o:canonical:ubuntu_linux:24.04::~~lts~~~`, in `virt-manager-5.0.0-2.fc42.noarch`.
SELinux is preventing rpc-virtqemud from 'getattr' accesses on the directory /dev/binderfs.

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

If you believe that rpc-virtqemud should be allowed getattr access on the binderfs directory 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 'rpc-virtqemud' --raw | audit2allow -M my-rpcvirtqemud
# semodule -X 300 -i my-rpcvirtqemud.pp

Additional Information:
Source Context                system_u:system_r:virtqemud_t:s0
Target Context                system_u:object_r:binderfs_t:s0
Target Objects                /dev/binderfs [ dir ]
Source                        rpc-virtqemud
Source Path                   rpc-virtqemud
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-41.41-1.fc42.noarch
Local Policy RPM              selinux-policy-targeted-41.41-1.fc42.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.14.9-300.fc42.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Thu May 29 14:27:53 UTC 2025
                              x86_64
Alert Count                   1
First Seen                    2025-06-06 14:04:46 BST
Last Seen                     2025-06-06 14:04:46 BST
Local ID                      5954f58d-c4ef-40f1-98b7-5443cca01d92

Raw Audit Messages
type=AVC msg=audit(1749215086.650:290): avc:  denied  { getattr } for  pid=66554 comm="rpc-virtqemud" path="/dev/binderfs" dev="binder" ino=1 scontext=system_u:system_r:virtqemud_t:s0 tcontext=system_u:object_r:binderfs_t:s0 tclass=dir permissive=1


Hash: rpc-virtqemud,virtqemud_t,binderfs_t,dir,getattr

Version-Release number of selected component:
selinux-policy-targeted-41.41-1.fc42.noarch

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing rpc-virtqemud from 'getattr' accesses on the directory /dev/binderfs.
package:        selinux-policy-targeted-41.41-1.fc42.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.14.9-300.fc42.x86_64
comment:        I created a VM with `neon-unstable-20250601-1146.iso`, whose type was `cpe:/o:canonical:ubuntu_linux:24.04::~~lts~~~`, in `virt-manager-5.0.0-2.fc42.noarch`.
component:      selinux-policy

Comment 1 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-06-06 13:07:28 UTC
Created attachment 2093200 [details]
File: description

Comment 2 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-06-06 13:07:29 UTC
Created attachment 2093201 [details]
File: os_info

Comment 3 Zdenek Pytela 2025-06-20 18:18:57 UTC
*** Bug 2374065 has been marked as a duplicate of this bug. ***

Comment 4 jjanasek 2025-12-19 08:48:17 UTC
*** Bug 2374161 has been marked as a duplicate of this bug. ***

Comment 5 Fedora Release Engineering 2026-05-06 13:09:49 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-09 03:49:03 UTC
Is this worth keeping open, or should I file a new reproduction in F44? I see similar from F43, in 2026-02, in SEAlert.