Bug 1200894 - SELinux is preventing login from read, write access on the chr_file /dev/dri/card0.
Summary: SELinux is preventing login from read, write access on the chr_file /dev/dri/...
Alias: None
Product: Fedora
Classification: Fedora
Component: kmscon
Version: 21
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Nicolas Chauvet (kwizart)
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:cf6c7f651560fb78e6d1bc84af5...
Depends On:
TreeView+ depends on / blocked
Reported: 2015-03-11 15:18 UTC by Paul W. Frields
Modified: 2015-10-29 08:22 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-10-29 08:22:00 UTC
Type: ---

Attachments (Terms of Use)

Description Paul W. Frields 2015-03-11 15:18:50 UTC
Description of problem:
I resumed from suspend on F21 x86_64 (Workstation/GNOME desktop), and was unable to see a password entry field when I typed. The screenlock/shield did not change and I could not move it to get a password entry field. However, my typng was accepted and the screen was unlocked.

SELinux is preventing login from read, write access on the chr_file /dev/dri/card0.

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

If you believe that login should be allowed read write access on the card0 chr_file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
# grep login /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:local_login_t:s0-s0:c0.c1023
Target Context                system_u:object_r:dri_device_t:s0
Target Objects                /dev/dri/card0 [ chr_file ]
Source                        login
Source Path                   login
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-105.3.fc21.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 3.18.7-200.fc21.x86_64 #1 SMP Wed
                              Feb 11 21:53:17 UTC 2015 x86_64 x86_64
Alert Count                   16421
First Seen                    2015-02-07 06:09:36 EST
Last Seen                     2015-03-11 11:10:13 EDT
Local ID                      0634e7d7-1cb2-4840-873c-3891a45aab2b

Raw Audit Messages
type=AVC msg=audit(1426086613.573:20098): avc:  denied  { read write } for  pid=11596 comm="login" path="/dev/dri/card0" dev="devtmpfs" ino=11862 scontext=system_u:system_r:local_login_t:s0-s0:c0.c1023 tcontext=system_u:object_r:dri_device_t:s0 tclass=chr_file permissive=0

Hash: login,local_login_t,dri_device_t,chr_file,read,write

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.3.0
hashmarkername: setroubleshoot
kernel:         3.18.7-200.fc21.x86_64
type:           libreport

Comment 1 Lukas Vrabec 2015-03-13 13:47:23 UTC
Any help here? 
Why login writing to /dev/dri/card0 ?

Comment 2 Karel Zak 2015-03-16 13:44:18 UTC
Do you really mean login(1) command? (So the text terminal/console login program.)

Maybe the user is talking about xserver/gdm :-)

Comment 3 Karel Zak 2015-03-16 13:46:48 UTC
Ah, I see comm="login" in audit log... Well, I have no clue why it works with /dev/dri/card0, PAM or so?

Comment 4 Giovanni Campagna 2015-03-31 02:59:15 UTC
Description of problem:
I don't know how this problem happened, but I would place my bet on a leaked file descriptor from kmscon, which spawned login.
I'm reporting this bug as a selinux bug through the tool, but most likely it's a kmscon issue.

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.3.0
hashmarkername: setroubleshoot
kernel:         3.19.2-201.fc21.x86_64
type:           libreport

Comment 5 Miroslav Grepl 2015-04-03 15:23:50 UTC
if you add a local policy, does it help?

Comment 6 Paul W. Frields 2015-04-06 18:19:32 UTC
Since doing a fresh install on this machine (again, F21), I haven't been able to reproduce the problem.  Maybe this was a bug elsewhere that's been fixed?

Comment 7 Lukas Vrabec 2015-04-07 13:58:58 UTC
Probably, we can close this for now.

Comment 8 Nicolas Chauvet (kwizart) 2015-10-29 08:22:00 UTC
Sorry, but I've missed this report, why would you think this would have been related to kmscon (the userspace console ?) This isn't the default console in fedora, so it's quite surprising that kmscon would be involved at all.

As per-the previous message, I'm closing now, but re-assigned to util-linux because of the login question.

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