Bug 2174567

Summary: SELinux is preventing rpmdb_migrate from 'execute_no_trans' accesses on the file /usr/bin/rm.
Product: [Fedora] Fedora Reporter: Ian Laurie <nixuser>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: dwalsh, lvrabec, mmalik, omosnacek, pkoncity, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:bad8af449d9a9f15c84bb567f15370495a8c9a7314b0ffc693ff45eba87a8407;VARIANT_ID=;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-02 09:25:10 UTC 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 Ian Laurie 2023-03-01 20:39:38 UTC
Description of problem:
Boot and login to Xfce.
SELinux is preventing rpmdb_migrate from 'execute_no_trans' accesses on the file /usr/bin/rm.

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

If you believe that rpmdb_migrate should be allowed execute_no_trans access on the rm file 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 'rpmdb_migrate' --raw | audit2allow -M my-rpmdbmigrate
# semodule -X 300 -i my-rpmdbmigrate.pp

Additional Information:
Source Context                system_u:system_r:rpmdb_t:s0
Target Context                system_u:object_r:bin_t:s0
Target Objects                /usr/bin/rm [ file ]
Source                        rpmdb_migrate
Source Path                   rpmdb_migrate
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           coreutils-9.1-11.fc38.x86_64
SELinux Policy RPM            selinux-policy-targeted-38.6-1.fc38.noarch
Local Policy RPM              selinux-policy-targeted-38.6-1.fc38.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.2.1-300.fc38.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Sun Feb 26 00:25:40 UTC 2023
                              x86_64
Alert Count                   1
First Seen                    2023-03-02 07:38:03 AEDT
Last Seen                     2023-03-02 07:38:03 AEDT
Local ID                      dd3f5b4f-18af-4e1f-8c5a-35c799c96a04

Raw Audit Messages
type=AVC msg=audit(1677703083.444:64): avc:  denied  { execute_no_trans } for  pid=643 comm="rpmdb_migrate" path="/usr/bin/rm" dev="sda3" ino=2383978 scontext=system_u:system_r:rpmdb_t:s0 tcontext=system_u:object_r:bin_t:s0 tclass=file permissive=0


Hash: rpmdb_migrate,rpmdb_t,bin_t,file,execute_no_trans

Version-Release number of selected component:
selinux-policy-targeted-38.6-1.fc38.noarch

Additional info:
reporter:       libreport-2.17.7
reason:         SELinux is preventing rpmdb_migrate from 'execute_no_trans' accesses on the file /usr/bin/rm.
package:        selinux-policy-targeted-38.6-1.fc38.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.2.1-300.fc38.x86_64
comment:        Boot and login to Xfce.
component:      selinux-policy

Comment 1 Ian Laurie 2023-03-01 20:39:40 UTC
Created attachment 1947314 [details]
File: description

Comment 2 Ian Laurie 2023-03-01 20:39:42 UTC
Created attachment 1947315 [details]
File: os_info

Comment 3 Ian Laurie 2023-03-01 20:42:06 UTC
I'm getting this on just about every login in fc38, with all updates applied from updates-testing (ie this instance isn't frozen).

Comment 4 Zdenek Pytela 2023-03-02 09:25:10 UTC

*** This bug has been marked as a duplicate of bug 2164752 ***