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 1888912 - SELinux policy change not visible to systemd until daemon-reexec
Summary: SELinux policy change not visible to systemd until daemon-reexec
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: David Tardon
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-16 08:36 UTC by Maciek Borzecki
Modified: 2021-05-18 14:54 UTC (History)
3 users (show)

Fixed In Version: systemd-239-44.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 14:54:22 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github systemd-rhel rhel-8 pull 140 0 None closed (#1888912) reload SELinux label cache on daemon-reload 2021-01-29 09:20:43 UTC
Github systemd systemd pull 14188 0 None closed core: reload SELinux label cache on daemon-reload 2021-01-29 09:20:43 UTC
Github systemd systemd pull 14781 0 None closed selinux: add trigger for policy reload to refresh internal selabel cache 2021-01-29 09:20:44 UTC

Description Maciek Borzecki 2020-10-16 08:36:02 UTC
Description of problem:

When SELinux policy loading modules that modify the allow rules for init_t, a daemon-reexec is needed for those rules to be applied. This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1197886 which was fixed systemd v245 in Fedora.

Version-Release number of selected component (if applicable):
systemd-239-31.el8_2.2.x86_64


How reproducible:
always


Steps to Reproduce:
1. install snapd from epel-8 (pulls in snapd-selinux)
2. install the lxd snap, a socket service for the snap is created during the install, the install fails
3. observe the following denial: avc:  denied  { create } for  pid=1 comm="systemd" name="unix.socket" scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=sock_file permissive=0
4. the rule is allowed by snapd-selinux module
5. run systemctl daemon-reexec
6. successfuly install the lxd snap again

Comment 1 David Tardon 2020-11-26 11:48:49 UTC
Note: I cannot try this on 8.2 because snapd--or, rather, snapd-selinux--cannot be installed due to a version clash with selinux-policy. And I cannot reproduce it on 8.3...

Comment 2 Lukáš Nykrýn 2021-01-25 14:02:00 UTC
fix merged to github master branch -> https://github.com/systemd-rhel/rhel-8/pull/140

Comment 9 errata-xmlrpc 2021-05-18 14:54:22 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 (Moderate: systemd security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2021:1611


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