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.

Description of problem:


Version-Release number of selected component (if applicable):
arpwatch-2.1a15-14.el6.x86_64
selinux-policy-3.7.19-231.el6.noarch
selinux-policy-doc-3.7.19-231.el6.noarch
selinux-policy-minimum-3.7.19-231.el6.noarch
selinux-policy-mls-3.7.19-231.el6.noarch
selinux-policy-targeted-3.7.19-231.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. get a RHEL-6.5 machine where targeted policy is active
2. service arpwatch start
3. search for AVCs

Actual results (enforcing mode):
----
type=SYSCALL msg=audit(11/03/2013 13:39:32.264:577) : arch=x86_64 syscall=socket success=no exit=-13(Permission denied) a0=10 a1=3 a2=c a3=3f1b38fed0 items=0 ppid=7237 pid=7238 auid=root uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=pts0 ses=9 comm=arpwatch exe=/usr/sbin/arpwatch subj=unconfined_u:system_r:arpwatch_t:s0 key=(null) 
type=AVC msg=audit(11/03/2013 13:39:32.264:577) : avc:  denied  { create } for  pid=7238 comm=arpwatch scontext=unconfined_u:system_r:arpwatch_t:s0 tcontext=unconfined_u:system_r:arpwatch_t:s0 tclass=netlink_socket 
----

Expected results:
 * no AVCs

Actual results (permissive mode);
----
type=SYSCALL msg=audit(11/03/2013 13:47:03.700:610) : arch=x86_64 syscall=socket success=yes exit=3 a0=10 a1=3 a2=c a3=3f1b38fed0 items=0 ppid=7384 pid=7385 auid=root uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=pts0 ses=9 comm=arpwatch exe=/usr/sbin/arpwatch subj=unconfined_u:system_r:arpwatch_t:s0 key=(null) 
type=AVC msg=audit(11/03/2013 13:47:03.700:610) : avc:  denied  { create } for  pid=7385 comm=arpwatch scontext=unconfined_u:system_r:arpwatch_t:s0 tcontext=unconfined_u:system_r:arpwatch_t:s0 tclass=netlink_socket 
----

We allow it in Fedora

#============= arpwatch_t ==============

#!!!! This avc is allowed in the current policy
allow arpwatch_t self:netlink_socket create;

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-2014-1568.html