Bug 2362879 - SELinux is preventing unbound-anchor from 'read' accesses on the file no-stub-resolv.conf.
Summary: SELinux is preventing unbound-anchor from 'read' accesses on the file no-stub...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 42
Hardware: x86_64
OS: Unspecified
medium
low
Target Milestone: ---
Assignee: Ondrej Mosnacek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:30aea9aefa226859263ee739590...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-29 11:43 UTC by Sam Varshavchik
Modified: 2025-05-28 01:56 UTC (History)
9 users (show)

Fixed In Version: selinux-policy-41.41-1.fc42
Clone Of:
Environment:
Last Closed: 2025-05-28 01:56:24 UTC
Type: ---
Embargoed:
zpytela: mirror+


Attachments (Terms of Use)
File: description (1.99 KB, text/plain)
2025-04-29 11:43 UTC, Sam Varshavchik
no flags Details
File: os_info (702 bytes, text/plain)
2025-04-29 11:43 UTC, Sam Varshavchik
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github fedora-selinux selinux-policy pull 2691 0 None open Allow named_t to read NetworkManager's runtime files 2025-05-13 12:36:12 UTC
Red Hat Issue Tracker FC-1637 0 None None None 2025-04-29 18:11:28 UTC

Description Sam Varshavchik 2025-04-29 11:43:53 UTC
Description of problem:
AVC occurs occasionally after waking the laptop from sleep.
SELinux is preventing unbound-anchor from 'read' accesses on the file no-stub-resolv.conf.

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

If you believe that unbound-anchor should be allowed read access on the no-stub-resolv.conf 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 'unbound-anchor' --raw | audit2allow -M my-unboundanchor
# semodule -X 300 -i my-unboundanchor.pp

Additional Information:
Source Context                system_u:system_r:named_t:s0
Target Context                system_u:object_r:NetworkManager_var_run_t:s0
Target Objects                no-stub-resolv.conf [ file ]
Source                        unbound-anchor
Source Path                   unbound-anchor
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-41.38-1.fc42.noarch
Local Policy RPM              selinux-policy-targeted-41.38-1.fc42.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.14.3-300.fc42.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Sun Apr 20 16:08:39 UTC 2025
                              x86_64
Alert Count                   2
First Seen                    2025-04-28 07:29:36 EDT
Last Seen                     2025-04-29 07:42:06 EDT
Local ID                      a07ff62e-21c3-4930-b016-e60994fc7462

Raw Audit Messages
type=AVC msg=audit(1745926926.638:13790): avc:  denied  { read } for  pid=95889 comm="unbound-anchor" name="no-stub-resolv.conf" dev="tmpfs" ino=14695 scontext=system_u:system_r:named_t:s0 tcontext=system_u:object_r:NetworkManager_var_run_t:s0 tclass=file permissive=0


Hash: unbound-anchor,named_t,NetworkManager_var_run_t,file,read

Version-Release number of selected component:
selinux-policy-targeted-41.38-1.fc42.noarch

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing unbound-anchor from 'read' accesses on the file no-stub-resolv.conf.
package:        selinux-policy-targeted-41.38-1.fc42.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.14.3-300.fc42.x86_64
comment:        AVC occurs occasionally after waking the laptop from sleep.
component:      selinux-policy

Comment 1 Sam Varshavchik 2025-04-29 11:43:56 UTC
Created attachment 2087734 [details]
File: description

Comment 2 Sam Varshavchik 2025-04-29 11:43:58 UTC
Created attachment 2087735 [details]
File: os_info

Comment 3 Fedora Update System 2025-05-13 19:17:49 UTC
FEDORA-2025-5e64167ac4 (selinux-policy-41.40-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-5e64167ac4

Comment 4 Fedora Update System 2025-05-14 02:07:49 UTC
FEDORA-2025-5e64167ac4 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-5e64167ac4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5e64167ac4

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

Comment 5 Fedora Update System 2025-05-15 01:55:55 UTC
FEDORA-2025-5e64167ac4 (selinux-policy-41.40-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2025-05-26 10:25:47 UTC
FEDORA-2025-cdfbb5ba42 (selinux-policy-41.41-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-cdfbb5ba42

Comment 7 Fedora Update System 2025-05-27 01:08:13 UTC
FEDORA-2025-cdfbb5ba42 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-cdfbb5ba42`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-cdfbb5ba42

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

Comment 8 Fedora Update System 2025-05-28 01:56:24 UTC
FEDORA-2025-cdfbb5ba42 (selinux-policy-41.41-1.fc42) has been pushed to the Fedora 42 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.