Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1931959 - SELinux is preventing systemd-hostnam from 'read' accesses on the file +dmi:id.
Summary: SELinux is preventing systemd-hostnam from 'read' accesses on the file +dmi:id.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 34
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e306ff31b8d62486f4c45769200...
: 1932436 1932682 1932683 1932688 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-23 16:22 UTC by Matt Fagnani
Modified: 2021-03-16 00:28 UTC (History)
15 users (show)

Fixed In Version: selinux-policy-3.14.7-25.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-16 00:28:55 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Matt Fagnani 2021-02-23 16:22:28 UTC 
Description of problem:
I was using a Fedora 34 KDE Plasma installation updated to 2021-2-22. I updated to systemd-248~rc1-2.fc34 from https://koji.fedoraproject.org/koji/buildinfo?buildID=1714025 I rebooted. systemd-hostnamed was denied reading +dmi:id as systemd-hostnamed was starting during boot. This denial happened on 2/2 boots with systemd-248~rc1-2.fc34, but it didn't happen with systemd-247.3-3.fc34 or earlier.

SELinux is preventing systemd-hostnam from 'read' accesses on the file +dmi:id.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that systemd-hostnam should be allowed read access on the +dmi:id file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'systemd-hostnam' --raw | audit2allow -M my-systemdhostnam
# semodule -X 300 -i my-systemdhostnam.pp

Additional Information:
Source Context                system_u:system_r:systemd_hostnamed_t:s0
Target Context                system_u:object_r:udev_var_run_t:s0
Target Objects                +dmi:id [ file ]
Source                        systemd-hostnam
Source Path                   systemd-hostnam
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-3.14.7-22.fc34.noarch
Local Policy RPM              selinux-policy-targeted-3.14.7-22.fc34.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 5.11.0-156.fc34.x86_64 #1 SMP Wed
                              Feb 17 08:31:59 UTC 2021 x86_64 x86_64
Alert Count                   12
First Seen                    2021-02-23 10:51:59 EST
Last Seen                     2021-02-23 11:10:44 EST
Local ID                      ced175e2-e99c-4001-aa55-60b9ee5a21d7

Raw Audit Messages
type=AVC msg=audit(1614096644.177:649): avc:  denied  { read } for  pid=1148 comm="systemd-hostnam" name="+dmi:id" dev="tmpfs" ino=1255 scontext=system_u:system_r:systemd_hostnamed_t:s0 tcontext=system_u:object_r:udev_var_run_t:s0 tclass=file permissive=0


Hash: systemd-hostnam,systemd_hostnamed_t,udev_var_run_t,file,read

Version-Release number of selected component:
selinux-policy-targeted-3.14.7-22.fc34.noarch

Additional info:
component:      selinux-policy
reporter:       libreport-2.14.0
hashmarkername: setroubleshoot
kernel:         5.11.0-156.fc34.x86_64
type:           libreport
Comment 1 Zdenek Pytela 2021-02-23 16:54:13 UTC 
I've submitted a Fedora PR to address the issue:
https://github.com/fedora-selinux/selinux-policy/pull/611
Comment 2 Matt Fagnani 2021-02-23 18:02:11 UTC 
(In reply to Zdenek Pytela from comment #1)
> I've submitted a Fedora PR to address the issue:
> https://github.com/fedora-selinux/selinux-policy/pull/611

Thanks. I ran the following commands to allow this systemd-hostnamed denial and rebooted.
sudo ausearch -c 'systemd-hostnam' --raw | audit2allow -M my-systemdhostnam
sudo semodule -X 300 -i my-systemdhostnam.pp

The following denial of systemd-hostnamed opening /run/udev/data/+dmi:id happened when systemd-hostnamed was starting during the next boot.
type=AVC msg=audit(1614101662.249:277): avc:  denied  { open } for  pid=902 comm="systemd-hostnam" path="/run/udev/data/+dmi:id" dev="tmpfs" ino=1159 scontext=system_u:system_r:systemd_hostnamed_t:s0 tcontext=system_u:object_r:udev_var_run_t:s0 tclass=file permissive=0

I ran the ausearch and semodule commands above again and rebooted. The following denial of systemd-hostnamed getattr accesses on /run/udev/data/+dmi:id happened when systemd-hostnamed was starting during the next boot.
type=AVC msg=audit(1614102325.443:274): avc:  denied  { getattr } for  pid=898 comm="systemd-hostnam" path="/run/udev/data/+dmi:id" dev="tmpfs" ino=1132 scontext=system_u:system_r:systemd_hostnamed_t:s0 tcontext=system_u:object_r:udev_var_run_t:s0 tclass=file permissive=0

The systemd-248-rc1 release notes mentioned a change in systemd-hostnamed reading from DMI tables which might be related to these denials.
"systemd-hostnamed now exports the "HardwareVendor" and "HardwareModel" D-Bus properties, which are supposed to contain a pair of cleaned up, human readable strings describing the system's vendor and model. It's typically sourced from the firmware's DMI tables, but may be augmented from a new hwdb database. hostnamectl shows this in the status output."
https://github.com/systemd/systemd/blob/v248-rc1/NEWS
Comment 3 Zdenek Pytela 2021-02-23 19:12:48 UTC 
Thank you, I've updated the commit message.
Comment 4 Fedora Update System 2021-02-24 10:09:28 UTC 
FEDORA-2021-ccd3bb057b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ccd3bb057b
Comment 5 Fedora Update System 2021-02-24 19:18:22 UTC 
FEDORA-2021-ccd3bb057b has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-ccd3bb057b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ccd3bb057b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Zdenek Pytela 2021-02-24 20:31:48 UTC 
*** Bug 1932436 has been marked as a duplicate of this bug. ***
Comment 7 Zdenek Pytela 2021-02-25 08:12:43 UTC 
*** Bug 1932688 has been marked as a duplicate of this bug. ***
Comment 8 Zdenek Pytela 2021-02-25 08:13:40 UTC 
*** Bug 1932683 has been marked as a duplicate of this bug. ***
Comment 9 Zdenek Pytela 2021-02-25 08:14:10 UTC 
*** Bug 1932682 has been marked as a duplicate of this bug. ***
Comment 10 Fedora Update System 2021-03-03 15:47:39 UTC 
FEDORA-2021-1cb3d5cac1 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-1cb3d5cac1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-1cb3d5cac1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 11 Peter Larsen 2021-03-04 14:44:07 UTC 
Similar problem has been detected:

Openining "Settings" in GnomeShell 4.0

hashmarkername: setroubleshoot
kernel:         5.10.19-200.fc33.x86_64
package:        selinux-policy-targeted-3.14.7-22.fc34.noarch
reason:         SELinux is preventing systemd-hostnam from 'read' accesses on the file +dmi:id.
type:           libreport
Comment 12 Fedora Update System 2021-03-12 18:56:59 UTC 
FEDORA-2021-1e99f2ed79 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-1e99f2ed79`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-1e99f2ed79

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 13 Fedora Update System 2021-03-16 00:28:55 UTC 
FEDORA-2021-1e99f2ed79 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.