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 1460480 - /usr/libexec/colord (colord_t) tries to access hwdb.bin (systemd_hwdb_etc_t)
Summary: /usr/libexec/colord (colord_t) tries to access hwdb.bin (systemd_hwdb_etc_t)
Keywords:
Status: CLOSED DUPLICATE of bug 1373082
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-11 01:08 UTC by Robert Scheck
Modified: 2019-06-28 13:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-12 11:46:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Robert Scheck 2017-06-11 01:08:11 UTC 
Description of problem:
type=AVC msg=audit(1495140135.407:133): avc:  denied  { read } for  pid=1861 comm="colord" name="hwdb.bin" dev="dm-0" ino=1838809 scontext=system_u:system_r:colord_t:s0 tcontext=system_u:object_r:systemd_hwdb_etc_t:s0 tclass=file
type=SYSCALL msg=audit(1495140135.407:133): arch=c000003e syscall=2 success=no exit=-13 a0=7fb3c7a822fb a1=80000 a2=1b6 a3=24 items=0 ppid=1 pid=1861 auid=4294967295 uid=995 gid=993 euid=995 suid=995 fsuid=995 egid=993 sgid=993 fsgid=993 tty=(none) ses=4294967295 comm="colord" exe="/usr/libexec/colord" subj=system_u:system_r:colord_t:s0 key=(null)
type=AVC msg=audit(1495140135.407:134): avc:  denied  { read } for  pid=1861 comm="colord" name="hwdb.bin" dev="dm-0" ino=1838809 scontext=system_u:system_r:colord_t:s0 tcontext=system_u:object_r:systemd_hwdb_etc_t:s0 tclass=file
type=SYSCALL msg=audit(1495140135.407:134): arch=c000003e syscall=2 success=no exit=-13 a0=7fb3c7a822fb a1=80000 a2=1b6 a3=24 items=0 ppid=1 pid=1861 auid=4294967295 uid=995 gid=993 euid=995 suid=995 fsuid=995 egid=993 sgid=993 fsgid=993 tty=(none) ses=4294967295 comm="colord" exe="/usr/libexec/colord" subj=system_u:system_r:colord_t:s0 key=(null)
type=SERVICE_START msg=audit(1495140135.412:135): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=colord comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.13.1-102.el7_3.16.noarch
colord-1.2.7-2.el7.x86_64

How reproducible:
Everytime, see above and below. Basically a system with GUI.

Actual results:
/usr/libexec/colord tries to access hwdb.bin

Expected results:
No AVC denied, but I have no idea if that should be allowed or not.
Comment 2 Milos Malik 2017-06-12 08:44:16 UTC 
I believe this bug is a duplicate of BZ#1373082.
Comment 3 Lukas Vrabec 2017-06-12 11:46:10 UTC 

*** This bug has been marked as a duplicate of bug 1373082 ***
Note You need to log in before you can comment on or make changes to this bug.