Bug 1373665 - SELinux is preventing mprotheap from using the 'execheap' accesses on a process.
Summary: SELinux is preventing mprotheap from using the 'execheap' accesses on a process.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 25
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5d6d12117143709ed7fcaa7dfe8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-06 22:33 UTC by Jeremy Cline
Modified: 2017-01-10 15:37 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-06 22:36:24 UTC
Type: ---


Attachments (Terms of Use)

Description Jeremy Cline 2016-09-06 22:33:43 UTC
Description of problem:
This denial appears to be happening on boot.
SELinux is preventing mprotheap from using the 'execheap' accesses on a process.

*****  Plugin allow_execheap (53.1 confidence) suggests   ********************

If you do not think mprotheap should need to map heap memory that is both writable and executable.
Then you need to report a bug. This is a potentially dangerous access.
Do
contact your security administrator and report this issue.

*****  Plugin catchall_boolean (42.6 confidence) suggests   ******************

If you want to allow selinuxuser to execheap
Then you must tell SELinux about this by enabling the 'selinuxuser_execheap' boolean.
You can read 'None' man page for more details.
Do
setsebool -P selinuxuser_execheap 1

*****  Plugin catchall (5.76 confidence) suggests   **************************

If you believe that mprotheap should be allowed execheap access on processes labeled unconfined_t 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 'mprotheap' --raw | audit2allow -M my-mprotheap
# semodule -X 300 -i my-mprotheap.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1
                              023
Target Context                unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1
                              023
Target Objects                Unknown [ process ]
Source                        mprotheap
Source Path                   mprotheap
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-211.fc25.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.8.0-0.rc4.git0.1.fc25.x86_64 #1
                              SMP Mon Aug 29 19:28:01 UTC 2016 x86_64 x86_64
Alert Count                   1
First Seen                    2016-09-05 10:40:27 EDT
Last Seen                     2016-09-05 10:40:27 EDT
Local ID                      dca3625b-e022-4385-a008-deb5bcf2f6f9

Raw Audit Messages
type=AVC msg=audit(1473086427.899:274): avc:  denied  { execheap } for  pid=5074 comm="mprotheap" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=process permissive=0


Hash: mprotheap,unconfined_t,unconfined_t,process,execheap

Version-Release number of selected component:
selinux-policy-3.13.1-211.fc25.noarch

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.8.0-0.rc4.git0.1.fc25.x86_64
type:           libreport

Potential duplicate: bug 1367939

Comment 1 Jeremy Cline 2016-09-06 22:36:24 UTC
Ah, it looks like this is caused by the kernel regression suite[0] and I failed to clear my SELinux denials. Sorry for the noise.

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1275007

Comment 2 Giulio 'juliuxpigface' 2016-10-11 20:03:09 UTC
Description of problem:
I'm not sure when did this pop up. I booted the laptop after an update, logged to Xfce and ran a kernel regression test. Then I found the notify on the panel.

Version-Release number of selected component:
selinux-policy-3.13.1-218.fc25.noarch

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.8.1-1.fc25.i686+PAE
type:           libreport

Comment 3 Zdenek Chmelar 2016-10-27 15:12:21 UTC
Description of problem:
Popped up during kernel regression test

Version-Release number of selected component:
selinux-policy-3.13.1-220.fc25.noarch

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.8.4-301.fc25.x86_64
type:           libreport

Comment 4 Zdenek Chmelar 2016-11-03 15:43:22 UTC
Description of problem:
Happened during kernel regression test run

Version-Release number of selected component:
selinux-policy-3.13.1-220.fc25.noarch

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.8.6-300.fc25.x86_64
type:           libreport

Comment 5 Shaun Assam 2017-01-10 15:37:32 UTC
Description of problem:
- Ran kernel regression test
- SELinux Alert appeared after paxtest passed and before posix_timers passed

Version-Release number of selected component:
selinux-policy-3.13.1-225.6.fc25.noarch

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.8.16-300.fc25.x86_64
type:           libreport


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