Bug 2063871
Summary: | AVC lldpad denied sendto scontext=system_u:system_r:lldpad_t:s0 tcontext=system_u:system_r:unconfined_service_t:s0 tclass=unix_dgram_socket | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Sandro Bonazzola <sbonazzo> | |
Component: | selinux-policy | Assignee: | Zdenek Pytela <zpytela> | |
Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 8.6 | CC: | amusil, bstinson, eraviv, gdeolive, jwboyer, lsurette, lvrabec, mburman, mmalik, mperina, msobczyk, srevivo, ssekidde, ycui, zpytela | |
Target Milestone: | rc | Keywords: | AutomationBlocker, Triaged, ZStream | |
Target Release: | 8.7 | |||
Hardware: | Unspecified | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | selinux-policy-3.14.3-99.el8 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 2082147 2095184 (view as bug list) | Environment: | ||
Last Closed: | 2022-11-08 10:44:11 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 2020997, 2082147, 2095184, 2111410 |
Description
Sandro Bonazzola
2022-03-14 14:42:38 UTC
Commit to backport: commit d45bd1720adf4e9819e725082cf6925fa946e909 Author: Zdenek Pytela <zpytela> Date: Tue Aug 24 19:40:25 2021 +0200 Allow lldpad send to unconfined_t over a unix dgram socket A similar problem probably appears on RHEL 9. Seems I overlooked the type actually is unconfined_service_t. Sandro, do you know which service lldpad tries to communicate with? ps -eo pid,ppid,fname,cmd,context | grep -e CONTEXT -e unconfined_service_t I've submitted a Fedora draft PR to assign file context for both /usr/libexec/vdsm/supervdsmd and vdsmd: https://github.com/fedora-selinux/selinux-policy/pull/1166 OK, based on above findings moving the bug to RHV for further investigation Here are reproducing steps for the iscsi issue: 1. Have a RHV hypervisor with iscsi storage 2. Move to Maintanence 3. SSH to host and apply correct selinux rules: chcon -t virtd_exec_t /usr/libexec/vdsm/vdsmd_init_common.sh chcon -t virtd_exec_t /usr/libexec/vdsm/supervdsmd chcon -t virtd_exec_t /usr/libexec/vdsm/vdsmd chcon -t virtd_exec_t /usr/libexec/vdsm/daemonAdapter 4. Reboot host and wait to restart finished 5. Activate the host -> after activation the host is switched to NonOperational, all iscsi storage domains report errors. This needs to be solved before we can fix the rules in default selinux policy and ask for backport to RHEL 8.6.z Hi, after some investigation it seems that the iscsi was coincidence. Could you please prepare the patch for selinux-context with following files having virtd_exec_t: /usr/libexec/vdsm/vdsmd_init_common.sh /usr/libexec/vdsm/supervdsmd /usr/libexec/vdsm/vdsmd /usr/libexec/vdsm/daemonAdapter We will also need 8.6 backport. Thanks (In reply to Ales Musil from comment #38) > Hi, > > after some investigation it seems that the iscsi was coincidence. Could you > please > prepare the patch for selinux-context with following files having > virtd_exec_t: > /usr/libexec/vdsm/vdsmd_init_common.sh > /usr/libexec/vdsm/supervdsmd > /usr/libexec/vdsm/vdsmd > /usr/libexec/vdsm/daemonAdapter > > We will also need 8.6 backport. The fix is on the way and should be in the next build. For a backport, please follow z-stream workflow. Additional commit to backport: commit 8ec1a669d99b1b0a86dbf4ac151e3b0f2a778eb1 (HEAD -> rawhide, upstream/rawhide) Author: Zdenek Pytela <zpytela> Date: Thu May 12 10:45:19 2022 +0200 Label more vdsm utils with virtd_exec_t 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 (selinux-policy bug fix and enhancement update), 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/RHBA-2022:7691 |