Bug 1800927
Summary: | SELinux is preventing /usr/lib/systemd/systemd-journald from 'read' accesses on the lnk_file /run/user/1000/systemd/units/invocation:dbus-:1.2-org.fedoraproject.Setroubleshootd@0.service. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 32 | CC: | awilliam, dwalsh, grepl.miroslav, hdegoede, kparal, lvrabec, plautrba, stransky, ttomasz, vmojzis, zpytela |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:481ca6e5756fbb5dfdd2515a735c14d9e9f6c018a089d28b950a984b3778e671;VARIANT_ID=workstation; | ||
Fixed In Version: | selinux-policy-3.14.5-32.fc32 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-30 00:17:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1812955 | ||
Bug Blocks: |
Description
Mikhail
2020-02-09 08:56:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32. *** Bug 1801121 has been marked as a duplicate of this bug. *** *** Bug 1802677 has been marked as a duplicate of this bug. *** Similar problem has been detected: I just upgraded to Fedora 32 and I'm spammed with these SELinux alerts right after boot. hashmarkername: setroubleshoot kernel: 5.6.0-0.rc3.git0.1.fc32.x86_64 package: selinux-policy-3.14.5-28.fc32.noarch reason: SELinux is preventing /usr/lib/systemd/systemd-journald from 'read' accesses on the lnk_file /run/user/1000/systemd/units/invocation:gnome-shell-x11.service. type: libreport I had about 300 occurrences of this alert in the last few days. This is by far the most frequent source of "New SELinux security alert" popups. Can we please do something about this? It's extremely frequent. *** Bug 1809993 has been marked as a duplicate of this bug. *** Kamil, I understand it needs to be addressed soon. commit 64e6995beda26de512045d73159054e274427a1a (HEAD -> rawhide, origin/rawhide) Author: Lukas Vrabec <lvrabec> Date: Mon Mar 23 14:56:22 2020 +0100 Allow systemd-journald to read user_tmp_t symlinks Resolves: rhbz#1800927 Similar problem has been detected: Not sure what specifically triggered this. Just found it when checking AVCs in my current boot. I've just booted to Workstation and done usual desktop-y stuff. hashmarkername: setroubleshoot kernel: 5.6.0-0.rc5.git0.2.fc32.x86_64 package: selinux-policy-3.14.5-31.fc32.noarch reason: SELinux is preventing systemd-journal from 'read' accesses on the lnk_file /run/user/1001/systemd/units/invocation:gnome-shell-wayland.service. type: libreport Similar problem has been detected: This SELinux Alert started to show after I upgraded my F31 KDE to F32. hashmarkername: setroubleshoot kernel: 5.6.0-0.rc7.git0.2.fc32.x86_64 package: selinux-policy-3.14.5-31.fc32.noarch reason: SELinux is preventing /usr/lib/systemd/systemd-journald from 'read' accesses on the lnk_file /run/user/1000/systemd/units/invocation:dbus-:1.2-org.fedoraproject.Setroubleshootd. type: libreport FEDORA-2020-32711482f7 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-32711482f7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-32711482f7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-32711482f7 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. I can confirm the update fixes this problem. Thanks Kamil for testing. |