Bug 2273707 - SELinux is preventing key.dns_resolve from 'read' accesses on the lnk_file log.
Summary: SELinux is preventing key.dns_resolve from 'read' accesses on the lnk_file log.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 38
Hardware: x86_64
OS: Unspecified
medium
unspecified
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c716104506b0941c7af72b5d8fc...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-05 19:27 UTC by Hilário Fochi Silveira
Modified: 2024-05-10 01:34 UTC (History)
9 users (show)

Fixed In Version: selinux-policy-38.33-1.fc38
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-05-10 01:34:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: description (1.95 KB, text/plain)
2024-04-05 19:27 UTC, Hilário Fochi Silveira
no flags Details
File: os_info (667 bytes, text/plain)
2024-04-05 19:27 UTC, Hilário Fochi Silveira
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github fedora-selinux selinux-policy pull 2075 0 None open Allow keyutils-dns-resolver connect to the system log service 2024-04-08 12:04:16 UTC

Description Hilário Fochi Silveira 2024-04-05 19:27:09 UTC
Description of problem:
It occurred after I started a nordvpn and used Firefox to browse
SELinux is preventing key.dns_resolve from 'read' accesses on the lnk_file log.

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

If you believe that key.dns_resolve should be allowed read access on the log lnk_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 'key.dns_resolve' --raw | audit2allow -M my-keydnsresolve
# semodule -X 300 -i my-keydnsresolve.pp

Additional Information:
Source Context                system_u:system_r:keyutils_dns_resolver_t:s0
Target Context                system_u:object_r:devlog_t:s0
Target Objects                log [ lnk_file ]
Source                        key.dns_resolve
Source Path                   key.dns_resolve
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-38.32-1.fc38.noarch
Local Policy RPM              selinux-policy-targeted-38.32-1.fc38.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.5.7-200.fc38.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Wed Oct 11 04:07:58 UTC 2023
                              x86_64
Alert Count                   35
First Seen                    2024-04-05 16:03:27 -03
Last Seen                     2024-04-05 16:24:46 -03
Local ID                      f8405328-4061-479b-84de-d0d38bb97be6

Raw Audit Messages
type=AVC msg=audit(1712345086.525:270): avc:  denied  { read } for  pid=5751 comm="key.dns_resolve" name="log" dev="devtmpfs" ino=198 scontext=system_u:system_r:keyutils_dns_resolver_t:s0 tcontext=system_u:object_r:devlog_t:s0 tclass=lnk_file permissive=0


Hash: key.dns_resolve,keyutils_dns_resolver_t,devlog_t,lnk_file,read

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

Additional info:
reporter:       libreport-2.17.11
type:           libreport
kernel:         6.5.7-200.fc38.x86_64
reason:         SELinux is preventing key.dns_resolve from 'read' accesses on the lnk_file log.
comment:        It occurred after I started a nordvpn and used Firefox to browse
component:      selinux-policy
hashmarkername: setroubleshoot
package:        selinux-policy-targeted-38.32-1.fc38.noarch
component:      selinux-policy

Comment 1 Hilário Fochi Silveira 2024-04-05 19:27:12 UTC
Created attachment 2025475 [details]
File: description

Comment 2 Hilário Fochi Silveira 2024-04-05 19:27:14 UTC
Created attachment 2025476 [details]
File: os_info

Comment 3 Fedora Update System 2024-04-24 12:25:59 UTC
FEDORA-2024-c92737ccc0 (selinux-policy-38.33-1.fc38) has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-c92737ccc0

Comment 4 Fedora Update System 2024-04-25 02:29:29 UTC
FEDORA-2024-c92737ccc0 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-c92737ccc0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-c92737ccc0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2024-05-10 01:34:04 UTC
FEDORA-2024-c92737ccc0 (selinux-policy-38.33-1.fc38) has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


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