Bug 2374198 - SELinux is preventing /usr/bin/nft from read, write access on the chr_file /dev/udmabuf.
Summary: SELinux is preventing /usr/bin/nft from read, write access on the chr_file /d...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 42
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:63fc212288634ca29a1905ab53f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-22 12:15 UTC by Agustín P
Modified: 2026-06-08 17:35 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-06-08 17:35:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: description (2.71 KB, text/plain)
2025-06-22 12:15 UTC, Agustín P
no flags Details
File: os_info (673 bytes, text/plain)
2025-06-22 12:15 UTC, Agustín P
no flags Details

Description Agustín P 2025-06-22 12:15:38 UTC
Description of problem:
It can be reproduced by running a simple container using podman compose in a rootless podman context.

```
services:
  app:
    image: hello-world
```

Using slirp4netns or none as `network_mode` rather than 'pasta' prevents this issue.
SELinux is preventing /usr/bin/nft from read, write access on the chr_file /dev/udmabuf.

*****  Plugin leaks (86.2 confidence) suggests   *****************************

If you want to ignore nft trying to read write access the udmabuf chr_file, because you believe it should not need this access.
Then you should report this as a bug.  
You can generate a local policy module to dontaudit this access.
Do
# ausearch -x /usr/bin/nft --raw | audit2allow -D -M my-nft
# semodule -X 300 -i my-nft.pp

*****  Plugin catchall (14.7 confidence) suggests   **************************

If you believe that nft should be allowed read write access on the udmabuf chr_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 'nft' --raw | audit2allow -M my-nft
# semodule -X 300 -i my-nft.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:iptables_t:s0-
                              s0:c0.c1023
Target Context                system_u:object_r:dma_device_t:s0
Target Objects                /dev/udmabuf [ chr_file ]
Source                        nft
Source Path                   /usr/bin/nft
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           nftables-1.1.1-3.fc42.x86_64
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-41.43-1.fc42.noarch
Local Policy RPM              
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.14.11-300.fc42.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Tue Jun 10 16:24:16 UTC 2025
                              x86_64
Alert Count                   4
First Seen                    2025-06-22 08:49:20 -03
Last Seen                     2025-06-22 08:49:20 -03
Local ID                      364cba51-ab8b-46f4-9b59-84f47ce8e19d

Raw Audit Messages
type=AVC msg=audit(1750592960.363:1873): avc:  denied  { read write } for  pid=30642 comm="nft" path="/dev/udmabuf" dev="devtmpfs" ino=155 scontext=unconfined_u:unconfined_r:iptables_t:s0-s0:c0.c1023 tcontext=system_u:object_r:dma_device_t:s0 tclass=chr_file permissive=0


type=SYSCALL msg=audit(1750592960.363:1873): arch=x86_64 syscall=execve success=yes exit=0 a0=7fb5a1153d70 a1=55c1ed743390 a2=7ffe4a041718 a3=8 items=0 ppid=30635 pid=30642 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=pts2 ses=3 comm=nft exe=/usr/bin/nft subj=unconfined_u:unconfined_r:iptables_t:s0-s0:c0.c1023 key=(null)

Hash: nft,iptables_t,dma_device_t,chr_file,read,write

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

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing /usr/bin/nft from read, write access on the chr_file /dev/udmabuf.
package:        selinux-policy-targeted-41.43-1.fc42.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.14.11-300.fc42.x86_64
component:      selinux-policy

Comment 1 Agustín P 2025-06-22 12:15:41 UTC
Created attachment 2094659 [details]
File: description

Comment 2 Agustín P 2025-06-22 12:15:43 UTC
Created attachment 2094660 [details]
File: os_info

Comment 3 Agustín P 2025-06-29 14:39:04 UTC
I wasn't able to reproduce this issue on my desktop (Fedora 42 KDE).

bug 2374197#c4 provides more details about this issue (that seems to be related to HyperV/hv_netvscc).

Comment 4 Fedora Release Engineering 2026-05-06 13:19:08 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Aoife Moloney 2026-06-08 17:35:55 UTC
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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