Bug 2299033 - SELinux is preventing chromium-browse from using the execheap access on a process.
Summary: SELinux is preventing chromium-browse from using the execheap access on a pro...
Keywords:
Status: CLOSED DUPLICATE of bug 2254434
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 39
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-20 17:00 UTC by Mario Smeh
Modified: 2024-07-31 06:24 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-31 06:24:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mario Smeh 2024-07-20 17:00:40 UTC
Description of problem:
SELinux is preventing chromium-browse from using the execheap access on a process.

Plugin: allow_execheap 
 The chromium-browse application attempted to change the access protection of
memory on the heap (e.g., allocated using malloc).  This is a potential security
problem.  Applications should not be doing this. Applications are sometimes
coded incorrectly and request this permission.  The SELinux Memory Protection
Tests web page explains how to remove this requirement.  If chromium-browse does
not work and you need it to work, you can configure SELinux temporarily to allow
this access until the application is fixed. Please file a bug report against
this package.

Version-Release number of selected component (if applicable):
chromium-common-0:126.0.6478.182-1.fc39.x86_64                                                                                                                                                           chromium-0:126.0.6478.182-1.fc39.x86_64 


How reproducible:


Steps to Reproduce:
1.Start chromium browser
2.
3.

Actual results:
SELinux alert

Expected results:
without SELinux alert

Additional info:

Comment 1 Kamil Páral 2024-07-31 06:24:50 UTC

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


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