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:
This is occurring on many RHEL 6 systems:
SELinux has prevented ip from loading a kernel module. All confined programs
that need to load kernel modules should have already had policy written for
them. If a compromised application tries to modify the kernel this AVC will be
generated. This is a serious issue. Your system may very well be compromised.


Version-Release number of selected component (if applicable):
iproute-2.6.32-16.el6.x86_64
kernel-2.6.32-131.4.1.el6.x86_64
selinux-policy-3.7.19-93.el6_1.2.noarch

How reproducible:
Often, several times per day

Steps to Reproduce:
1. Try to connect to a VPN connection with NetworkManager
2.
3.
  
Actual results:
The connection fails

Expected results:
The connection should work

Additional info:
This happened only as a result of recent software updates in the past week.  This should be marked a regression.

Created attachment 519924 [details]
selinux alert message

Created attachment 519925 [details]
yum recent log, one of these packages causes this issue

Yes this is a kernel userspace issue that we will be covering up in 

selinux-policy-3.7.19-107.el6

Nothing was actually blocked.

If you want to try out the policy you can grab it from 

http://people.redhat.com/dwalsh/SELinux/RHEL6

What wonderful heroism, Dan.  Thanks for saving the day.

Seems to be a duplicete of 726339? Can we close it?

go ahead