Bug 1979448

Summary: SELinux is preventing gdb from 'read' accesses on the file index.
Product: [Fedora] Fedora Reporter: Angie <bellecodeur>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: alex.go4more, dwalsh, grepl.miroslav, i3100686, lvrabec, mmalik, omosnace, vini9x, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1283961ae5a91206a7d88d60cc2c3c2d06f5beb332cae24844173a3cbddf105b;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-09 15:24:58 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:

Description Angie 2021-07-06 05:33:06 UTC
Description of problem:
SELinux is preventing gdb from 'read' accesses on the file index.

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

If you believe that gdb should be allowed read access on the index 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:xdm_var_lib_t:s0
Target Objects                index [ file ]
Source                        gdb
Source Path                   gdb
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-34.12-1.fc34.noarch
Local Policy RPM              selinux-policy-targeted-34.12-1.fc34.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 5.12.13-300.fc34.x86_64 #1 SMP Wed
                              Jun 23 16:18:11 UTC 2021 x86_64 x86_64
Alert Count                   1
First Seen                    2021-07-01 12:00:05 PDT
Last Seen                     2021-07-01 12:00:05 PDT
Local ID                      800704ce-f2f7-4c63-b5d5-635b88c965ea

Raw Audit Messages
type=AVC msg=audit(1625166005.757:796): avc:  denied  { read } for  pid=2494 comm="gdb" name="index" dev="nvme0n1p6" ino=370250 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xdm_var_lib_t:s0 tclass=file permissive=0


Hash: gdb,abrt_t,xdm_var_lib_t,file,read

Version-Release number of selected component:
selinux-policy-targeted-34.12-1.fc34.noarch

Additional info:
component:      selinux-policy
reporter:       libreport-2.15.2
hashmarkername: setroubleshoot
kernel:         5.12.13-300.fc34.x86_64
type:           libreport

Potential duplicate: bug 1929814

Comment 1 i3100686 2021-09-08 09:22:41 UTC
Similar problem has been detected:

These error messages appeared when the desktop was loade after the reboot consequent to KDE Plasma installation

hashmarkername: setroubleshoot
kernel:         5.11.12-300.fc34.x86_64
package:        selinux-policy-targeted-34.16-1.fc34.noarch
reason:         SELinux is preventing gdb from 'read' accesses on the file user.
type:           libreport

Comment 2 vini9x 2021-10-28 11:54:28 UTC
Similar problem has been detected:

Right after login, the troubleshooter alerted me of this problem.

hashmarkername: setroubleshoot
kernel:         5.14.11-200.fc34.x86_64
package:        selinux-policy-targeted-34.21-1.fc34.noarch
reason:         SELinux is preventing gdb from 'read' accesses on the file user.
type:           libreport

Comment 3 Zdenek Pytela 2021-12-09 15:24:58 UTC

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