Bug 2327878 - SELinux is preventing /usr/sbin/virtqemud from 'getattr' accesses on the directory /dev/binderfs.
Summary: SELinux is preventing /usr/sbin/virtqemud from 'getattr' accesses on the dire...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 41
Hardware: x86_64
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9cb0c8113fd8c33f59497d3b9b0...
: 2343444 2364279 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-21 18:38 UTC by Renich Bon Ciric
Modified: 2025-12-16 17:44 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-12-16 17:44:47 UTC
Type: ---
Embargoed:
zpytela: mirror+


Attachments (Terms of Use)
File: description (2.35 KB, text/plain)
2024-11-21 18:38 UTC, Renich Bon Ciric
no flags Details
File: os_info (754 bytes, text/plain)
2024-11-21 18:38 UTC, Renich Bon Ciric
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-1682 0 None None None 2025-05-21 14:15:46 UTC

Description Renich Bon Ciric 2024-11-21 18:38:50 UTC
Description of problem:
This is 7 of 10 reports I am going to make. 

I've installed CentOS Stream 10 on UEFI using virt-install:

virt-install --connect=qemu:///system --name=cs10 --vcpus=2 --memory=4096 --boot=uefi --osinfo=centos-stream9 --location=https://mirror.stream.centos.org/10-stream/BaseOS/x86_64/os/

It installed correctly but I saw some SELInux issues as soon as it started. Yet, it installed correctly. 

Now, I am trying to boot it and 10 SELinux warnings come up. I will make a report for each one of them. 

I've also, taken a screenshot and recorded a short video of a strange issue. Every time I turn off the machine and back on, the SELInux label changes. I restore them, repeat and the same happens. It's clearer in t
he video which I will attach to the first bug report only. 

Thank you. 

Relates to bug: 2327872

https://bugzilla.redhat.com/show_bug.cgi?id=2327872
SELinux is preventing /usr/sbin/virtqemud from 'getattr' accesses on the directory /dev/binderfs.

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

If you believe that 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                   /usr/sbin/virtqemud
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           libvirt-daemon-driver-qemu-10.6.0-5.fc41.x86_64
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-41.25-1.fc41.noarch
Local Policy RPM              selinux-policy-targeted-41.25-1.fc41.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 6.11.8-300.fc41.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Thu Nov 14 20:37:39 UTC 2024
                              x86_64
Alert Count                   8
First Seen                    2024-11-21 11:59:59 CST
Last Seen                     2024-11-21 12:22:47 CST
Local ID                      826ae7f0-5dfe-43ae-a5cf-8ce66b6c4f91

Raw Audit Messages
type=AVC msg=audit(1732213367.621:2436): avc:  denied  { getattr } for  pid=88716 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


type=SYSCALL msg=audit(1732213367.621:2436): arch=x86_64 syscall=newfstatat success=yes exit=0 a0=ffffff9c a1=7f8e1c094ed0 a2=7f8e2abfded0 a3=0 items=0 ppid=88715 pid=88716 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=rpc-virtqemud exe=/usr/sbin/virtqemud subj=system_u:system_r:virtqemud_t:s0 key=(null)

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

Version-Release number of selected component:
selinux-policy-targeted-41.25-1.fc41.noarch

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing /usr/sbin/virtqemud from 'getattr' accesses on the directory /dev/binderfs.
package:        selinux-policy-targeted-41.25-1.fc41.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.11.8-300.fc41.x86_64
component:      selinux-policy

Comment 1 Renich Bon Ciric 2024-11-21 18:38:53 UTC
Created attachment 2059151 [details]
File: description

Comment 2 Renich Bon Ciric 2024-11-21 18:38:55 UTC
Created attachment 2059152 [details]
File: os_info

Comment 3 Alessandro Astone 2025-04-18 13:02:14 UTC
Sorry, /usr/sbin/virtqemud failing to access /dev/binderfs has nothing to do with waydroid.

/dev/binderfs is a regular kernel device that waydroid happens to use. Its selinux label is defined by selinux-policy and not by waydroid.

Comment 4 Zdenek Pytela 2025-05-06 06:27:54 UTC
*** Bug 2343444 has been marked as a duplicate of this bug. ***

Comment 5 Zdenek Pytela 2025-05-06 06:28:01 UTC
*** Bug 2364279 has been marked as a duplicate of this bug. ***

Comment 6 Adam Williamson (Red Hat non-Fedora) 2025-12-02 01:43:02 UTC
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
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 '41'.

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 41 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 7 Samyak Jain (RedHat) 2025-12-16 17:44:47 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.