RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1748519 - avc: podman run --security-opt label=type:svirt_qemu_net_t
Summary: avc: podman run --security-opt label=type:svirt_qemu_net_t
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: container-selinux
Version: 8.1
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: rc
: 8.2
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1734579 1764318 1779787
TreeView+ depends on / blocked
 
Reported: 2019-09-03 18:49 UTC by Ed Santiago
Modified: 2022-05-06 01:57 UTC (History)
5 users (show)

Fixed In Version: container-selinux-2.123.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1764318 1779787 (view as bug list)
Environment:
Last Closed: 2020-04-28 15:47:35 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-28433 0 None None None 2022-05-06 01:57:37 UTC
Red Hat Product Errata RHSA-2020:1650 0 None None None 2020-04-28 15:48:20 UTC

Description Ed Santiago 2019-09-03 18:49:20 UTC 
The following command emits no output on RHEL8, but generates an AVC and (incorrectly) exits 0:

   # podman run --rm --security-opt label=type:svirt_qemu_net_t registry.access.redhat.com/rhel7/rhel:latest date
   # echo $?
   0

/var/log/audit/audit.log shows:

   type=AVC msg=audit(1567536261.639:82): avc:  denied  { read write } for  pid=5062 comm="date" path="/dev/null" dev="tmpfs" ino=38157 scontext=system_u:system_r:svirt_qemu_net_t:s0:c805,c868 tcontext=system_u:object_r:container_file_t:s0:c805,c868 tclass=chr_file permissive=0
   type=AVC msg=audit(1567536261.639:82): avc:  denied  { write } for  pid=5062 comm="date" path="pipe:[36973]" dev="pipefs" ino=36973
scontext=system_u:system_r:svirt_qemu_net_t:s0:c805,c868 tcontext=unconfined_u:system_r:container_runtime_t:s0 tclass=fifo_file permissive=0
   type=AVC msg=audit(1567536261.639:82): avc:  denied  { write } for  pid=5062 comm="date" path="pipe:[36974]" dev="pipefs" ino=36974
scontext=system_u:system_r:svirt_qemu_net_t:s0:c805,c868 tcontext=unconfined_u:system_r:container_runtime_t:s0 tclass=fifo_file permissive=0

It works fine when setenforce->0

podman-1.4.2-2.module+el8.1.0+4016+4220c060.x86_64
container-selinux-2.107-2.module+el8.1.0+4016+4220c060.noarch
selinux-policy-3.14.3-19.el8.noarch

kernel 4.18.0-141.el8.x86_64

In case it's relevant, this is a system that I've been using for FIPS testing. However, FIPS mode is disabled and I've done several reboots since disabling it:

   # fips-mode-setup --check
   FIPS mode is disabled.
Comment 1 Daniel Walsh 2019-09-05 14:41:14 UTC 
I just updated container-selinux-2.116.0-1.gitc5ef5ac.fc31 in Fedora to block this transition.

Jindrich we will need an updated container-selinux package with this fix for RHEL8.1

This git checkin should be built for RHEL8.1.*

c5ef5ac658a0d616d53b81272694e778a2115b29
Comment 2 Daniel Walsh 2019-09-05 14:41:57 UTC 
This is definitely NOT a blocker.
Comment 12 Daniel Walsh 2020-03-21 11:43:29 UTC 
This looks correct to me.  We don't want containers running in a VM's label.
Comment 15 errata-xmlrpc 2020-04-28 15:47:35 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1650
Note You need to log in before you can comment on or make changes to this bug.