Bug 2299824

Summary: SELinux is preventing code from using the 'execheap' accesses on a process.
Product: [Fedora] Fedora Reporter: scapy <sajalsafalsharma1234>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 40CC: dwalsh, lvrabec, mmalik, omosnacek, pkoncity, sajalsafalsharma1234, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:9e8e1018a7f89f9eae5b0693b0a4acb99687f84d0fcbcb7ec06459337b6f1200;VARIANT_ID=budgie;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-07-25 11:56:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: description
none
File: os_info none

Description scapy 2024-07-25 11:22:57 UTC
Description of problem:
this problem occurred in vscode started sometimes it also happens when extention tab is opened in vscode i am using flatpak version from flathub some also happens with rpm version provided by microsoft some and i resently noticed some behaviour in chrome and as vscode is based on elctron which is based on chromium this can be also case if it. this less common in chrome i only seen it one time compare to vscode maybe some problem is also present in other electron based apps no mater its a flatpak or native rpm
SELinux is preventing code from using the 'execheap' accesses on a process.

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

If you do not think code 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.

Do
setsebool -P selinuxuser_execheap 1

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

If you believe that code 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 'code' --raw | audit2allow -M my-code
# semodule -X 300 -i my-code.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:unconfined_t:s0-
                              s0:c0.c1023
Target Context                unconfined_u:unconfined_r:unconfined_t:s0-
                              s0:c0.c1023
Target Objects                Unknown [ process ]
Source                        code
Source Path                   code
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-40.24-1.fc40.noarch
Local Policy RPM              selinux-policy-targeted-40.24-1.fc40.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.9.9-200.fc40.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Thu Jul 11 19:29:01 UTC 2024
                              x86_64
Alert Count                   348
First Seen                    2024-07-25 16:29:01 IST
Last Seen                     2024-07-25 16:29:41 IST
Local ID                      ec07d14c-fe9f-406e-92d3-54a547a77a63

Raw Audit Messages
type=AVC msg=audit(1721905181.64:579): avc:  denied  { execheap } for  pid=6479 comm="code" 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: code,unconfined_t,unconfined_t,process,execheap

Version-Release number of selected component:
selinux-policy-targeted-40.24-1.fc40.noarch

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing code from using the 'execheap' accesses on a process.
package:        selinux-policy-targeted-40.24-1.fc40.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.9.9-200.fc40.x86_64
comment:        this problem occurred when vscode started sometimes it also happens when extension tab is opened in vscode i am using flatpak version from flathub some also happens with rpm version provided by Microsoft i also recently noticed some behavior in chrome and as vscode is based on electron which is based on chromium this can be also reason. this less common in chrome i only seen it one time compare to vscode maybe same problem is also present in other electron based apps no mater its a flatpak or native rpm
component:      selinux-policy

Comment 1 scapy 2024-07-25 11:23:00 UTC
Created attachment 2040377 [details]
File: description

Comment 2 scapy 2024-07-25 11:23:02 UTC
Created attachment 2040378 [details]
File: os_info

Comment 3 Zdenek Pytela 2024-07-25 11:56:03 UTC

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