Bug 2443825 - Selinux failure for bootupctl
Summary: Selinux failure for bootupctl
Keywords:
Status: POST
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: rawhide
Hardware: Unspecified
OS: Linux
high
medium
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-03-02 14:04 UTC by Cristian Le
Modified: 2026-04-21 09:08 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:
zpytela: mirror+


Attachments (Terms of Use)
avc.txt (3.52 KB, text/plain)
2026-03-02 14:05 UTC, Cristian Le
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github fedora-selinux selinux-policy pull 3162 0 None Draft Allow bootupcl nnp transition to mount_t 2026-04-20 15:49:24 UTC
Red Hat Issue Tracker FC-3269 0 None None None 2026-03-03 16:21:16 UTC

Description Cristian Le 2026-03-02 14:04:37 UTC
Started to get these selinux failure for bootpctl (part of bootc)

```
----
type=AVC msg=audit(02/27/26 15:09:37.739:2040) : avc:  denied  { nnp_transition nosuid_transition } for  pid=13078 comm=bootupctl scontext=system_u:system_r:install_t:s0:c75,c789 tcontext=system_u:system_r:mount_t:s0:c75,c789 tclass=process2 permissive=0 
----
type=SELINUX_ERR msg=audit(02/27/26 15:09:37.739:2041) : op=security_bounded_transition seresult=denied oldcontext=system_u:system_r:install_t:s0:c75,c789 newcontext=system_u:system_r:mount_t:s0:c75,c789
```

Is it known or tracked?

Reproducible: Always

Comment 1 Cristian Le 2026-03-02 14:05:24 UTC
Created attachment 2131676 [details]
avc.txt

Comment 2 Zdenek Pytela 2026-04-20 15:49:25 UTC
Hi,

I've prepared a PR, but reading the description again I have a question: Which service executes bootupctl here?
It is a confined command, so there rather should be a transition.

$ matchpathcon /usr/bin/bootupctl
/usr/bin/bootupctl      system_u:object_r:bootupd_exec_t:s0

Comment 3 Cristian Le 2026-04-21 09:08:06 UTC
Afaict it is happening somewhere in our testing codepath of `/tests/provision/bootc`. We don't call `bootupctl` directly but something in `podman (machine|build)` does.

Maybe we can provide you a reproducer:
- From tmt repo
- Run the test file `tests/provision/bootc/test.sh`
- Get the avc log (not really sure how this is done)


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