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 698923 - selinux prevents kadmin from setsched operation
Summary: selinux prevents kadmin from setsched operation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-22 09:59 UTC by Ondrej Moriš
Modified: 2012-12-04 13:10 UTC (History)
2 users (show)

Fixed In Version: selinux-policy-3.7.19-96.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 10:07:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1511 0 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2011-12-06 00:39:17 UTC

Description Ondrej Moriš 2011-04-22 09:59:55 UTC
Description of problem:

Selinux is preventing kadmin from setched operation. Even though this denial has (probably) not any harmfull effect (i.e. everything works fine), I am quite sure that the test triggering this AVC does not do anything specific or unsual and hence there is probably missing rule / transition in the policy.

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

selinux-policy-targeted-3.7.19-84.el6.noarch
selinux-policy-3.7.19-84.el6.noarch

How reproducible:

Always.

Steps to Reproduce:

1. Run RHTS test /CoreOS/openldap/Sanity/integration-kerberos.
2. Run ausearch -m AVC -ts recent.
  
Actual results:

type=AVC msg=audit(1303374113.787:46063): avc:  denied  { setsched } for  pid=6402 comm="kadmind" scontext=unconfined_u:system_r:kadmind_t:s0 tcontext=unconfined_u:system_r:kadmind_t:s0 tclass=process

Expected results:

No AVC.

Additional info:

I am not sure if such a reproducer is correct. If not, I will be more than happy to provide a more detailed one. Just ask.

Comment 1 Daniel Walsh 2011-04-22 11:37:11 UTC
I fixed this in F15 and F16 policy.  Needs back port to RHEL5 and RHEL6 as well as F14

Comment 2 Miroslav Grepl 2011-05-27 11:56:55 UTC
Fixed in selinux-policy-3.7.19-96.el6

Comment 5 errata-xmlrpc 2011-12-06 10:07:32 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.

http://rhn.redhat.com/errata/RHBA-2011-1511.html


Note You need to log in before you can comment on or make changes to this bug.