Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionParikshit Khedekar
2018-12-03 10:07:13 UTC
Description of problem:
On an AWS t3.micro instance system marks following SELinux errors for NVM devices
$ sudo sealert -l ef9fbeb6-358c-4e20-8a3e-e65cd860cba5
SELinux is preventing /usr/sbin/rpc.mountd from read access on the blk_file nvme0n1p2.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that rpc.mountd should be allowed read access on the nvme0n1p2 blk_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 'rpc.mountd' --raw | audit2allow -M my-rpcmountd
# semodule -i my-rpcmountd.pp
Additional Information:
Source Context system_u:system_r:nfsd_t:s0
Target Context system_u:object_r:nvme_device_t:s0
Target Objects nvme0n1p2 [ blk_file ]
Source rpc.mountd
Source Path /usr/sbin/rpc.mountd
Port <Unknown>
Host ip-10-215-213-105.eu-west-1.compute.internal
Source RPM Packages nfs-utils-1.3.0-0.61.el7.x86_64
Target RPM Packages
Policy RPM selinux-policy-3.13.1-229.el7_6.5.noarch
Selinux Enabled True
Policy Type targeted
Enforcing Mode Enforcing
Host Name ip-10-215-213-105.eu-west-1.compute.internal
Platform Linux ip-10-215-213-105.eu-west-1.compute.internal
3.10.0-957.el7.x86_64 #1 SMP Thu Oct 4 20:48:51
UTC 2018 x86_64 x86_64
Alert Count 29
First Seen 2018-09-17 18:21:14 UTC
Last Seen 2018-11-14 14:33:20 UTC
Local ID ef9fbeb6-358c-4e20-8a3e-e65cd860cba5
Raw Audit Messages
type=AVC msg=audit(1542206000.948:39139): avc: denied { read } for pid=15281 comm="rpc.mountd" name="nvme0n1p2" dev="devtmpfs" ino=10945 scontext=system_u:system_r:nfsd_t:s0 tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file permissive=0
type=SYSCALL msg=audit(1542206000.948:39139): arch=x86_64 syscall=open success=no exit=EACCES a0=557e2e055b80 a1=80000 a2=0 a3=0 items=0 ppid=1 pid=15281 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=rpc.mountd exe=/usr/sbin/rpc.mountd subj=system_u:system_r:nfsd_t:s0 key=(null)
Hash: rpc.mountd,nfsd_t,nvme_device_t,blk_file,read
Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-229.el7_6.5.noarch
How reproducible:
On Red Hat Enterprise Linux 7.6
Steps to Reproduce:
1. Update to selinux-policy-3.13.1-229.el7_6.5.noarch on AWS t3.micro instances with NVM devices
2. check the sealert
3.
Actual results:
Hash: rpc.mountd,nfsd_t,nvme_device_t,blk_file,read are prevented from read access by Selinux.
Expected results:
It should allow it.
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:2127
Description of problem: On an AWS t3.micro instance system marks following SELinux errors for NVM devices $ sudo sealert -l ef9fbeb6-358c-4e20-8a3e-e65cd860cba5 SELinux is preventing /usr/sbin/rpc.mountd from read access on the blk_file nvme0n1p2. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that rpc.mountd should be allowed read access on the nvme0n1p2 blk_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 'rpc.mountd' --raw | audit2allow -M my-rpcmountd # semodule -i my-rpcmountd.pp Additional Information: Source Context system_u:system_r:nfsd_t:s0 Target Context system_u:object_r:nvme_device_t:s0 Target Objects nvme0n1p2 [ blk_file ] Source rpc.mountd Source Path /usr/sbin/rpc.mountd Port <Unknown> Host ip-10-215-213-105.eu-west-1.compute.internal Source RPM Packages nfs-utils-1.3.0-0.61.el7.x86_64 Target RPM Packages Policy RPM selinux-policy-3.13.1-229.el7_6.5.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name ip-10-215-213-105.eu-west-1.compute.internal Platform Linux ip-10-215-213-105.eu-west-1.compute.internal 3.10.0-957.el7.x86_64 #1 SMP Thu Oct 4 20:48:51 UTC 2018 x86_64 x86_64 Alert Count 29 First Seen 2018-09-17 18:21:14 UTC Last Seen 2018-11-14 14:33:20 UTC Local ID ef9fbeb6-358c-4e20-8a3e-e65cd860cba5 Raw Audit Messages type=AVC msg=audit(1542206000.948:39139): avc: denied { read } for pid=15281 comm="rpc.mountd" name="nvme0n1p2" dev="devtmpfs" ino=10945 scontext=system_u:system_r:nfsd_t:s0 tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file permissive=0 type=SYSCALL msg=audit(1542206000.948:39139): arch=x86_64 syscall=open success=no exit=EACCES a0=557e2e055b80 a1=80000 a2=0 a3=0 items=0 ppid=1 pid=15281 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=rpc.mountd exe=/usr/sbin/rpc.mountd subj=system_u:system_r:nfsd_t:s0 key=(null) Hash: rpc.mountd,nfsd_t,nvme_device_t,blk_file,read Version-Release number of selected component (if applicable): selinux-policy-3.13.1-229.el7_6.5.noarch How reproducible: On Red Hat Enterprise Linux 7.6 Steps to Reproduce: 1. Update to selinux-policy-3.13.1-229.el7_6.5.noarch on AWS t3.micro instances with NVM devices 2. check the sealert 3. Actual results: Hash: rpc.mountd,nfsd_t,nvme_device_t,blk_file,read are prevented from read access by Selinux. Expected results: It should allow it. Additional info: