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.
Bug 1752943 - dlm_controld needs permission to read /dev/random
Summary: dlm_controld needs permission to read /dev/random
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: selinux-policy
Version: 8.1
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: 8.2
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-17 15:58 UTC by Nate Straz
Modified: 2020-04-28 16:41 UTC (History)
7 users (show)

Fixed In Version: selinux-policy-3.14.3-22.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:41:06 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1773 0 None None None 2020-04-28 16:41:28 UTC

Description Nate Straz 2019-09-17 15:58:45 UTC 
Description of problem:

During gfs2 growfs testing, lvm refreshes storage changes across the cluster with dlm_controld.  In that process dlm_controld calls uuid_generate() from libuuid, which reads /dev/random and fails with the following AVC error

time->Wed Aug 21 15:50:23 2019
type=PROCTITLE msg=audit(1566420623.015:488): proctitle=646C6D5F636F6E74726F6C64002D730030
type=SYSCALL msg=audit(1566420623.015:488): arch=c000003e syscall=21 success=no exit=-13 a0=7f6816dd44d4 a1=4 a2=55fd6dfa2ec0 a3=55fd6d997010 items=0 ppid=1 pid=7279 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dlm_controld" exe="/usr/sbin/dlm_controld" subj=system_u:system_r:dlm_controld_t:s0 key=(null)
type=AVC msg=audit(1566420623.015:488): avc:  denied  { read } for  pid=7279 comm="dlm_controld" name="random" dev="devtmpfs" ino=8812 scontext=system_u:system_r:dlm_controld_t:s0 tcontext=system_u:object_r:random_device_t:s0 tclass=chr_file permissive=0

This does not cause a failure to refresh the logical volumes, nor causes gfs2_growfs to fail.  It will leave messages in the audit log which customers might raise concerns about.

Version-Release number of selected component (if applicable):
selinux-policy-3.14.3-20.el8.noarch
dlm-4.0.9-3.el8.x86_64


How reproducible:
Easily

Steps to Reproduce:
1. Run growfs test
2.
3.

Actual results:


Expected results:


Additional info:
Comment 10 errata-xmlrpc 2020-04-28 16:41:06 UTC 
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-2020:1773
Note You need to log in before you can comment on or make changes to this bug.