Bug 2338718 - SELinux is preventing totem-video-thu from read, write access on the chr_file /dev/udmabuf.
Summary: SELinux is preventing totem-video-thu from read, write access on the chr_file...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 41
Hardware: x86_64
OS: Unspecified
medium
low
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4fb6f628821fe896899da4d8600...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-01-18 05:52 UTC by richugireesh
Modified: 2025-04-01 14:19 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-04-01 14:19:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: description (1.98 KB, text/plain)
2025-01-18 05:52 UTC, richugireesh
no flags Details
File: os_info (754 bytes, text/plain)
2025-01-18 05:52 UTC, richugireesh
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github fedora-selinux selinux-policy pull 2580 0 None open Allow thumbnailer read and write the dma device 2025-02-20 19:41:45 UTC

Description richugireesh 2025-01-18 05:52:49 UTC
Description of problem:
Whenever I add a new video file to the system, this has happened.
SELinux is preventing totem-video-thu from read, write access on the chr_file /dev/udmabuf.

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

If you believe that totem-video-thu 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 'totem-video-thu' --raw | audit2allow -M my-totemvideothu
# semodule -X 300 -i my-totemvideothu.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023
Target Context                system_u:object_r:dma_device_t:s0
Target Objects                /dev/udmabuf [ chr_file ]
Source                        totem-video-thu
Source Path                   totem-video-thu
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-41.28-1.fc41.noarch
Local Policy RPM              selinux-policy-targeted-41.28-1.fc41.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.12.9-200.fc41.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Thu Jan 9 16:05:40 UTC 2025 x86_64
Alert Count                   14
First Seen                    2025-01-18 10:35:32 IST
Last Seen                     2025-01-18 11:15:12 IST
Local ID                      90d279cd-efb3-4ff6-a1be-e6056046e517

Raw Audit Messages
type=AVC msg=audit(1737179112.717:412): avc:  denied  { read write } for  pid=9348 comm="totem-video-thu" path="/dev/udmabuf" dev="devtmpfs" ino=152 scontext=unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023 tcontext=system_u:object_r:dma_device_t:s0 tclass=chr_file permissive=0


Hash: totem-video-thu,thumb_t,dma_device_t,chr_file,read,write

Version-Release number of selected component:
selinux-policy-targeted-41.28-1.fc41.noarch

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing totem-video-thu from read, write access on the chr_file /dev/udmabuf.
package:        selinux-policy-targeted-41.28-1.fc41.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.12.9-200.fc41.x86_64
comment:        Whenever I add a new video file to the system, this has happened.
component:      selinux-policy

Comment 1 richugireesh 2025-01-18 05:52:52 UTC
Created attachment 2066534 [details]
File: description

Comment 2 richugireesh 2025-01-18 05:52:54 UTC
Created attachment 2066535 [details]
File: os_info


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