Bug 1554396 - SELinux is preventing dmesg from 'map' accesses on the file /etc/ld.so.cache.
Summary: SELinux is preventing dmesg from 'map' accesses on the file /etc/ld.so.cache.
Keywords:
Status: CLOSED DUPLICATE of bug 1543153
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 27
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d4f321ef67a5790eedb484aceef...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-12 15:30 UTC by Mark Tinberg
Modified: 2018-03-24 18:55 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-03-24 18:55:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mark Tinberg 2018-03-12 15:30:35 UTC
Description of problem:
Applied most recent updates to F27 using GNOME Software Center, after reboot several utilites reported this error
Several utilities reported the same error after the most recent round of updates on F27

SELinux is preventing dmesg from 'map' accesses on the file /etc/ld.so.cache.

*****  Plugin restorecon (94.8 confidence) suggests   ************************

If you want to fix the label. 
/etc/ld.so.cache default label should be ld_so_cache_t.
Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly.
Do
# /sbin/restorecon -v /etc/ld.so.cache

*****  Plugin catchall_labels (5.21 confidence) suggests   *******************

If you want to allow dmesg to have map access on the ld.so.cache file
Then you need to change the label on /etc/ld.so.cache
Do
# semanage fcontext -a -t FILE_TYPE '/etc/ld.so.cache'
where FILE_TYPE is one of the following: dmesg_exec_t, fonts_cache_t, fonts_t, ld_so_cache_t, ld_so_t, lib_t, locale_t, prelink_exec_t, textrel_shlib_t.
Then execute:
restorecon -v '/etc/ld.so.cache'


*****  Plugin catchall (1.44 confidence) suggests   **************************

If you believe that dmesg should be allowed map access on the ld.so.cache 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 'dmesg' --raw | audit2allow -M my-dmesg
# semodule -X 300 -i my-dmesg.pp

Additional Information:
Source Context                system_u:system_r:dmesg_t:s0-s0:c0.c1023
Target Context                system_u:object_r:etc_t:s0
Target Objects                /etc/ld.so.cache [ file ]
Source                        dmesg
Source Path                   dmesg
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           glibc-2.26-26.fc27.x86_64 glibc-2.26-26.fc27.i686
Policy RPM                    selinux-policy-3.13.1-283.26.fc27.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.15.6-300.fc27.x86_64 #1 SMP Mon
                              Feb 26 18:43:03 UTC 2018 x86_64 x86_64
Alert Count                   1
First Seen                    2018-03-12 10:01:30 CDT
Last Seen                     2018-03-12 10:01:30 CDT
Local ID                      faeba518-14c7-4ef4-9cf5-bee6248fddc7

Raw Audit Messages
type=AVC msg=audit(1520866890.764:257): avc:  denied  { map } for  pid=19083 comm="dmesg" path="/etc/ld.so.cache" dev="dm-0" ino=33293592 scontext=system_u:system_r:dmesg_t:s0-s0:c0.c1023 tcontext=system_u:object_r:etc_t:s0 tclass=file permissive=0


Hash: dmesg,dmesg_t,etc_t,file,map

Version-Release number of selected component:
selinux-policy-3.13.1-283.26.fc27.noarch

Additional info:
component:      selinux-policy
reporter:       libreport-2.9.3
hashmarkername: setroubleshoot
kernel:         4.15.6-300.fc27.x86_64
type:           libreport

Comment 1 Lukas Vrabec 2018-03-24 18:55:42 UTC

*** This bug has been marked as a duplicate of bug 1543153 ***


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