Bug 1520897

Summary:	/dev/drm_dp_aux* devices should have a more specific label than device_t
Product:	Red Hat Enterprise Linux 7	Reporter:	Zdenek Pytela <zpytela>
Component:	selinux-policy	Assignee:	Lukas Vrabec <lvrabec>
Status:	CLOSED ERRATA	QA Contact:	Milos Malik <mmalik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	lvrabec, mgrepl, mmalik, mthacker, plautrba, ssekidde
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	selinux-policy-3.13.1-182.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 12:47:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Zdenek Pytela 2017-12-05 12:31:36 UTC

Description of problem:
The RHEL7 STIG requires that all device files in /dev have specific SELinux file types other than the device_t type:

http://rhel7stig.readthedocs.io/en/latest/medium.html#v-72039-all-system-device-files-must-be-correctly-labeled-to-prevent-unauthorized-modification-rhel-07-020900

As the /dev/drm_dp_aux* files have the generic device_t file type, conformance to the RHEL-07-020900 STIG rule on hosts with Intel Corporation HD Graphics 630 controllers fails.

Version-Release number of selected component (if applicable):


How reproducible:
Always with this hardware or a similar one

Steps to Reproduce:
1. restorecon -Rv /dev
2. find /dev -context '*:device_t:*' \( -type c -o -type b \) -print0 | xargs -0 ls -lsaZ


Actual results:
crw-------. root root system_u:object_r:device_t:s0    /dev/drm_dp_aux0
crw-------. root root system_u:object_r:device_t:s0    /dev/drm_dp_aux1
crw-------. root root system_u:object_r:device_t:s0    /dev/drm_dp_aux2


Expected results:
<no files with device_t labels>

Additional info:

Comment 10 errata-xmlrpc 2018-04-10 12:47:26 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-2018:0763