Bug 1397092 - selinux blocks screenlocker to use required resources
Summary: selinux blocks screenlocker to use required resources
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 25
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-21 15:24 UTC by Helio Chissini de Castro
Modified: 2017-12-12 10:28 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:28:26 UTC
Type: Bug


Attachments (Terms of Use)

Description Helio Chissini de Castro 2016-11-21 15:24:49 UTC
Qt QSGRenderThread uses system resources to keep the lock transition files when desktop ( KDE PLasma ) is locked/non logged.

Using proprietary nvidia/ati drivers, selinux is blocking the access of this resources making unable to unlock the desktop unless using terminal loginctl workaround.

Confirmed that add access to the resources system returns to work.

Log of the resulting problem:

SELinux is preventing QSGRenderThread from execute access on the file 2F7661722F6C69622F7364646D2F233230353738353038202864656C6574656429.

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

If you believe that QSGRenderThread should be allowed execute access on the 2F7661722F6C69622F7364646D2F233230353738353038202864656C6574656429 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 'QSGRenderThread' --raw | audit2allow -M my-QSGRenderThread
# semodule -X 300 -i my-QSGRenderThread.pp

Additional Information:
Source Context                system_u:system_r:xdm_t:s0-s0:c0.c1023
Target Context                system_u:object_r:xdm_var_lib_t:s0
Target Objects                2F7661722F6C69622F7364646D2F2332303537383530382028
                              64656C6574656429 [ file ]
Source                        QSGRenderThread
Source Path                   QSGRenderThread
Port                          <Unknown>
Host                          trex.bmw-carit.intra
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-220.fc25.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     trex.bmw-carit.intra
Platform                      Linux trex.bmw-carit.intra 4.8.4-301.fc25.x86_64
                              #1 SMP Tue Oct 25 00:01:49 UTC 2016 x86_64 x86_64
Alert Count                   4
First Seen                    2016-11-07 17:34:11 CET
Last Seen                     2016-11-10 17:03:58 CET
Local ID                      a8824324-a04f-4054-8d8a-1f7563cf4d19

Raw Audit Messages
type=AVC msg=audit(1478793838.690:1679): avc:  denied  { execute } for  pid=13927 comm="QSGRenderThread" path=2F7661722F6C69622F7364646D2F233230353738353038202864656C6574656429 dev="dm-0" ino=20578508 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xdm_var_lib_t:s0 tclass=file permissive=0


Hash: QSGRenderThread,xdm_t,xdm_var_lib_t,file,execute

Comment 1 Gilboa Davara 2017-01-09 17:52:06 UTC
I can no longer start sddm w/ Fedora 25.

SELinux is preventing QSGRenderThread from execute access on the file 2F7661722F6C69622F7364646D2F23353236393538202864656C6574656429.

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

If you believe that QSGRenderThread should be allowed execute access on the 2F7661722F6C69622F7364646D2F23353236393538202864656C6574656429 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 'QSGRenderThread' --raw | audit2allow -M my-QSGRenderThread
# semodule -X 300 -i my-QSGRenderThread.pp


Additional Information:
Source Context                system_u:system_r:xdm_t:s0-s0:c0.c1023
Target Context                system_u:object_r:xdm_var_lib_t:s0
Target Objects                2F7661722F6C69622F7364646D2F2335323639353820286465
                              6C6574656429 [ file ]
Source                        QSGRenderThread
Source Path                   QSGRenderThread
Port                          <Unknown>
Host                          gilboa-wx-dev
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-225.3.fc25.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     gilboa-wx-dev
Platform                      Linux gilboa-wx-dev 4.8.15-300.fc25.x86_64 #1 SMP
                              Thu Dec 15 23:10:23 UTC 2016 x86_64 x86_64
Alert Count                   16
First Seen                    2016-12-12 11:16:54 IST
Last Seen                     2017-01-09 19:49:39 IST
Local ID                      826ed34b-2d3e-4373-8205-d6870ad8fb22

Raw Audit Messages
type=AVC msg=audit(1483984179.345:1571): avc:  denied  { execute } for  pid=5176 comm="QSGRenderThread" path=2F7661722F6C69622F7364646D2F23353236393538202864656C6574656429 dev="dm-3" ino=526958 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xdm_var_lib_t:s0 tclass=file permissive=0

Comment 2 Gregory Seaborn 2017-02-16 03:26:26 UTC
I am getting very similar SELinux Alerts:

SELinux is preventing sddm-greeter from read access on the file core_pattern.

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

If you believe that sddm-greeter should be allowed read access on the core_pattern 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 'sddm-greeter' --raw | audit2allow -M my-sddmgreeter
# semodule -X 300 -i my-sddmgreeter.pp

Additional Information:
Source Context                system_u:system_r:xdm_t:s0-s0:c0.c1023
Target Context                system_u:object_r:usermodehelper_t:s0
Target Objects                core_pattern [ file ]
Source                        sddm-greeter
Source Path                   sddm-greeter
Port                          <Unknown>
Host                          localhost.localdomain
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-225.6.fc25.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     localhost.localdomain
Platform                      Linux localhost.localdomain 4.9.9-200.fc25.x86_64
                              #1 SMP Thu Feb 9 17:28:13 UTC 2017 x86_64 x86_64
Alert Count                   1
First Seen                    2017-02-15 22:20:31 EST
Last Seen                     2017-02-15 22:20:31 EST
Local ID                      93c5abd1-1a10-4253-ba7f-28cbbf045f06

Raw Audit Messages
type=AVC msg=audit(1487215231.247:153): avc:  denied  { read } for  pid=1058 comm="sddm-greeter" name="core_pattern" dev="proc" ino=14422 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:usermodehelper_t:s0 tclass=file permissive=0


Hash: sddm-greeter,xdm_t,usermodehelper_t,file,read


SELinux is preventing QSGRenderThread from execute access on the file 2F7661722F6C69622F7364646D2F2332343930343437202864656C6574656429.

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

If you believe that QSGRenderThread should be allowed execute access on the 2F7661722F6C69622F7364646D2F2332343930343437202864656C6574656429 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 'QSGRenderThread' --raw | audit2allow -M my-QSGRenderThread
# semodule -X 300 -i my-QSGRenderThread.pp

Additional Information:
Source Context                system_u:system_r:xdm_t:s0-s0:c0.c1023
Target Context                system_u:object_r:xdm_var_lib_t:s0
Target Objects                2F7661722F6C69622F7364646D2F2332343930343437202864
                              656C6574656429 [ file ]
Source                        QSGRenderThread
Source Path                   QSGRenderThread
Port                          <Unknown>
Host                          localhost.localdomain
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-225.6.fc25.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     localhost.localdomain
Platform                      Linux localhost.localdomain 4.9.9-200.fc25.x86_64
                              #1 SMP Thu Feb 9 17:28:13 UTC 2017 x86_64 x86_64
Alert Count                   1
First Seen                    2017-02-15 22:20:32 EST
Last Seen                     2017-02-15 22:20:32 EST
Local ID                      c0e9f833-1722-4c1e-b04a-7bc5c9537fad

Raw Audit Messages
type=AVC msg=audit(1487215232.480:156): avc:  denied  { execute } for  pid=1058 comm="QSGRenderThread" path=2F7661722F6C69622F7364646D2F2332343930343437202864656C6574656429 dev="sda3" ino=2490447 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xdm_var_lib_t:s0 tclass=file permissive=0


Hash: QSGRenderThread,xdm_t,xdm_var_lib_t,file,execute

Comment 3 Gregory Seaborn 2017-02-16 03:30:34 UTC
I am running Fedora 25 with KDE Plasma Version 5.8.5.  

Kernel Version is 4.9.9-200.fc25.x86_64.

Am using Nvidia proprietary drivers.  

Thanks, GregoryS

Comment 4 Fedora End Of Life 2017-11-16 19:31:06 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-12-12 10:28:26 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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