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.

Bug 1189185

Summary: apcupsd >= 3.14.13 avc denial for sysfs_t
Product: Red Hat Enterprise Linux 7 Reporter: Adam Kropelin <akropel1>
Component: selinux-policyAssignee: Simon Sekidde <ssekidde>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: akropel1, lvrabec, mgrepl, mmalik, plautrba, pvrabec, ssekidde
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-3.13.1-40.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 10:25:50 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:
Attachments:
Description Flags
local policy file for apcupsd libusb usage
none
Output from "ausearch -m avc -m user_avc -m selinux_err -i -ts today" none

Description Adam Kropelin 2015-02-04 16:08:09 UTC
Created attachment 988166 [details]
local policy file for apcupsd libusb usage

Beginning with version 3.14.13, apcupsd utilizes libusb. This requires an selinux policy update to allow the daemon access to /sys/bus/usb.

aureport for relevant events:

982. 02/04/2015 10:59:57 apcupsd system_u:system_r:apcupsd_t:s0 257 dir read system_u:object_r:sysfs_t:s0 denied 628
983. 02/04/2015 10:59:57 apcupsd system_u:system_r:apcupsd_t:s0 4 lnk_file read system_u:object_r:sysfs_t:s0 denied 629
984. 02/04/2015 10:59:57 apcupsd system_u:system_r:apcupsd_t:s0 4 file getattr system_u:object_r:sysfs_t:s0 denied 629
985. 02/04/2015 10:59:57 apcupsd system_u:system_r:apcupsd_t:s0 2 file read system_u:object_r:sysfs_t:s0 denied 630
986. 02/04/2015 10:59:57 apcupsd system_u:system_r:apcupsd_t:s0 2 file open system_u:object_r:sysfs_t:s0 denied 630

A local policy to allow sysfs access for apcupsd is attached. If there is a standard set of rules for general libusb clients, it would be appropriate to apply those instead.

Comment 1 Milos Malik 2015-02-04 16:11:03 UTC
Please provide more information:

# ausearch -m avc -m user_avc -m selinux_err -i -ts today

Comment 3 Adam Kropelin 2015-02-04 16:18:31 UTC
Created attachment 988168 [details]
Output from "ausearch -m avc -m user_avc -m selinux_err -i -ts today"

Comment 4 Milos Malik 2015-02-05 08:10:36 UTC
It's too late for RHEL-7.1.

Comment 12 errata-xmlrpc 2015-11-19 10:25:50 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://rhn.redhat.com/errata/RHBA-2015-2300.html