Bug 2217261 - SELinux is preventing gdb from 'read' accesses on the chr_file renderD128.
Summary: SELinux is preventing gdb from 'read' accesses on the chr_file renderD128.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 38
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1037e9e314ab8138adb0012eefe...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-25 16:23 UTC by Reginald Johnson
Modified: 2023-06-26 06:51 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-26 06:51:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: description (1.86 KB, text/plain)
2023-06-25 16:23 UTC, Reginald Johnson
no flags Details
File: os_info (709 bytes, text/plain)
2023-06-25 16:23 UTC, Reginald Johnson
no flags Details

Description Reginald Johnson 2023-06-25 16:23:06 UTC
Description of problem:
SELinux is preventing gdb from 'read' accesses on the chr_file renderD128.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that gdb should be allowed read access on the renderD128 chr_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:
# ausearch -c 'gdb' --raw | audit2allow -M my-gdb
# semodule -X 300 -i my-gdb.pp

Additional Information:
Source Context                system_u:system_r:abrt_t:s0-s0:c0.c1023
Target Context                system_u:object_r:dri_device_t:s0
Target Objects                renderD128 [ chr_file ]
Source                        gdb
Source Path                   gdb
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-38.17-1.fc38.noarch
Local Policy RPM              selinux-policy-targeted-38.17-1.fc38.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.3.8-200.fc38.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Thu Jun 15 02:15:40 UTC 2023
                              x86_64
Alert Count                   6
First Seen                    2023-06-25 21:36:36 IST
Last Seen                     2023-06-25 21:40:47 IST
Local ID                      06211c9d-96c6-4934-afc5-b9165e669801

Raw Audit Messages
type=AVC msg=audit(1687709447.205:409): avc:  denied  { read } for  pid=30581 comm="gdb" name="renderD128" dev="devtmpfs" ino=547 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:dri_device_t:s0 tclass=chr_file permissive=0


Hash: gdb,abrt_t,dri_device_t,chr_file,read

Version-Release number of selected component:
selinux-policy-targeted-38.17-1.fc38.noarch

Additional info:
reporter:       libreport-2.17.10
reason:         SELinux is preventing gdb from 'read' accesses on the chr_file renderD128.
package:        selinux-policy-targeted-38.17-1.fc38.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.3.8-200.fc38.x86_64
component:      selinux-policy

Comment 1 Reginald Johnson 2023-06-25 16:23:09 UTC
Created attachment 1972506 [details]
File: description

Comment 2 Reginald Johnson 2023-06-25 16:23:11 UTC
Created attachment 1972507 [details]
File: os_info

Comment 3 Zdenek Pytela 2023-06-26 06:51:54 UTC
It is required to turn this boolean on to allow abrt execute its gdb handler and be able to troubleshoot further:

  # setsebool -P abrt_handle_event on

and subsequently report another bug for the affected component.

This boolean will be turned on by default in the future Fedora releases.
Refer to abrt_handle_event_selinux(8) for more information.


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