Bug 2277456 - SELinux is preventing abrt-dump-journ from 'write' accesses on the sock_file io.systemd.Home.
Summary: SELinux is preventing abrt-dump-journ from 'write' accesses on the sock_file ...
Keywords:
Status: CLOSED DUPLICATE of bug 2265927
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 40
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a7ebe5d62b0552fb1babfb9e9dd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-27 05:05 UTC by saberfaith
Modified: 2024-04-29 09:11 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-04-29 09:11:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: description (2.03 KB, text/plain)
2024-04-27 05:09 UTC, saberfaith
no flags Details
File: os_info (682 bytes, text/plain)
2024-04-27 05:14 UTC, saberfaith
no flags Details

Description saberfaith 2024-04-27 05:05:11 UTC
Description of problem:
I upgraded from Fedora 39 to Fedora 40 and when I rebooted I received this error message shortly after loggin in
SELinux is preventing abrt-dump-journ from 'write' accesses on the sock_file io.systemd.Home.

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

If you believe that abrt-dump-journ should be allowed write access on the io.systemd.Home sock_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 'abrt-dump-journ' --raw | audit2allow -M my-abrtdumpjourn
# semodule -X 300 -i my-abrtdumpjourn.pp

Additional Information:
Source Context                system_u:system_r:abrt_dump_oops_t:s0
Target Context                system_u:object_r:systemd_userdbd_runtime_t:s0
Target Objects                io.systemd.Home [ sock_file ]
Source                        abrt-dump-journ
Source Path                   abrt-dump-journ
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-40.16-1.fc40.noarch
Local Policy RPM              selinux-policy-targeted-40.16-1.fc40.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.8.7-300.fc40.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Wed Apr 17 19:21:08 UTC 2024
                              x86_64
Alert Count                   16
First Seen                    2024-04-26 21:17:24 -05
Last Seen                     2024-04-26 21:17:25 -05
Local ID                      4501dc49-af25-4bd9-8670-a6d41a7ef174

Raw Audit Messages
type=AVC msg=audit(1714184245.839:254): avc:  denied  { write } for  pid=4041 comm="abrt-dump-journ" name="io.systemd.Home" dev="tmpfs" ino=2186 scontext=system_u:system_r:abrt_dump_oops_t:s0 tcontext=system_u:object_r:systemd_userdbd_runtime_t:s0 tclass=sock_file permissive=0


Hash: abrt-dump-journ,abrt_dump_oops_t,systemd_userdbd_runtime_t,sock_file,write

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

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing abrt-dump-journ from 'write' accesses on the sock_file io.systemd.Home.
package:        selinux-policy-targeted-40.16-1.fc40.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.8.7-300.fc40.x86_64
comment:        I upgraded from Fedora 39 to Fedora 40 and when I rebooted I received this error message shortly after loggin in
component:      selinux-policy

Comment 1 saberfaith 2024-04-27 05:09:46 UTC
Created attachment 2029563 [details]
File: description

Comment 2 saberfaith 2024-04-27 05:14:16 UTC
Created attachment 2029564 [details]
File: os_info

Comment 3 Zdenek Pytela 2024-04-29 09:11:49 UTC

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


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