Bug 715093 - SELinux is preventing /sbin/ethtool from read, write access on the file /run/lock/lmt-invoc.lock.
Summary: SELinux is preventing /sbin/ethtool from read, write access on the file /run/...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: wireless-tools
Version: 19
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: setroubleshoot_trace_hash:24f31ebf429...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-21 20:33 UTC by my_linux
Modified: 2015-02-17 13:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 13:47:11 UTC
Type: ---


Attachments (Terms of Use)

Description my_linux 2011-06-21 20:33:33 UTC
SELinux is preventing /sbin/ethtool from read, write access on the file /run/lock/lmt-invoc.lock.

*****  Plugin catchall (50.5 confidence) suggests  ***************************

If you believe that ethtool should be allowed read write access on the lmt-invoc.lock 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:
# grep ethtool /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

*****  Plugin leaks (50.5 confidence) suggests  ******************************

If you want to ignore ethtool trying to read write access the lmt-invoc.lock file, because you believe it should not need this access.
Then you should report this as a bug.  
You can generate a local policy module to dontaudit this access.
Do
# grep /sbin/ethtool /var/log/audit/audit.log | audit2allow -D -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:ifconfig_t:s0
Target Context                system_u:object_r:var_lock_t:s0
Target Objects                /run/lock/lmt-invoc.lock [ file ]
Source                        ethtool
Source Path                   /sbin/ethtool
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           wireless-tools-29-6.1.fc15
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.16-26.fc15
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 2.6.38.8-32.fc15.x86_64 #1 SMP Mon
                              Jun 13 19:49:05 UTC 2011 x86_64 x86_64
Alert Count                   10
First Seen                    Tue 21 Jun 2011 09:32:04 PM BST
Last Seen                     Tue 21 Jun 2011 09:32:06 PM BST
Local ID                      0c1de29f-c45f-4381-b600-8e1ebd4a6232

Raw Audit Messages
type=AVC msg=audit(1308688326.233:136): avc:  denied  { read write } for  pid=3229 comm="iwconfig" path="/run/lock/lmt-invoc.lock" dev=tmpfs ino=27541 scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:object_r:var_lock_t:s0 tclass=file


type=SYSCALL msg=audit(1308688326.233:136): arch=x86_64 syscall=execve success=yes exit=0 a0=216aa10 a1=2179530 a2=2152e20 a3=8 items=0 ppid=3228 pid=3229 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=iwconfig exe=/sbin/iwconfig subj=system_u:system_r:ifconfig_t:s0 key=(null)

Hash: ethtool,ifconfig_t,var_lock_t,file,read,write

audit2allow

#============= ifconfig_t ==============
allow ifconfig_t var_lock_t:file { read write };

audit2allow -R

#============= ifconfig_t ==============
allow ifconfig_t var_lock_t:file { read write };

Comment 1 Daniel Walsh 2011-06-22 14:54:43 UTC
Is this a leaked file descriptor?

How is /run/lock/lmt-invoc.lock created?  In an init script?

Comment 2 Fedora End Of Life 2013-04-03 18:13:06 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 3 Fedora End Of Life 2015-01-09 16:41:57 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 4 Fedora End Of Life 2015-02-17 13:47:11 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.