Bug 1427896 - modprobe doesn't work
Summary: modprobe doesn't work
Keywords:
Status: CLOSED DUPLICATE of bug 1427409
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-01 13:21 UTC by Jaroslav Škarvada
Modified: 2017-04-28 14:15 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-28 14:15:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Škarvada 2017-03-01 13:21:46 UTC
Description of problem:
I am not allowed to modprobe module from the command line, which seems strange.

Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-225.10.fc25.noarch

How reproducible:
Always

Steps to Reproduce:
1. modprobe vboxdrv
2. setenforce 0
3. modprobe vboxdrv
4. echo $?

Actual results:
modprobe: ERROR: could not insert 'vboxdrv': Permission denied
0

Expected results:
0

Additional info:
Why I am not allowed to modprobe the module from the command line? Shouldn't it run as unconfined? It's not service.

Comment 1 Jaroslav Škarvada 2017-03-01 13:23:09 UTC
I.e.:
# setenforce 1
# modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Permission denied
# setenforce 0
# modprobe vboxdrv

# lsmod | grep vboxdrv
vboxdrv               434176  0

Comment 2 Jaroslav Škarvada 2017-03-01 13:24:21 UTC
type=AVC msg=audit(1488374245.943:319): avc:  denied  { module_load } for  pid=26087 comm="modprobe" path="/usr/lib/modules/4.9.11-200.fc25.x86_64/extra/VirtualBox/vboxdrv.ko" dev="dm-3" ino=2534 scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=system_u:object_r:modules_object_t:s0 tclass=system permissive=1

Comment 3 Jaroslav Škarvada 2017-03-03 11:55:14 UTC
Also systemd-modules-load.service is failing due to this bug.

Comment 4 Jaroslav Škarvada 2017-03-03 11:55:54 UTC
Tagged as regression, because it worked in the past.

Comment 5 Lukas Vrabec 2017-04-28 14:15:04 UTC

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


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