Bug 2196008
Summary: | regression | flooding avc: denied { setcap } | chromium-113.0.5672.63-1.el8 | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Leon Fauster <leonfauster> |
Component: | chromium | Assignee: | Than Ngo <than> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel8 | CC: | spotrh, than, tpopela, yaneti, zpytela |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | chromium-113.0.5672.126-1.fc37 chromium-113.0.5672.126-1.fc38 chromium-113.0.5672.126-1.el9 chromium-113.0.5672.126-1.el7 chromium-113.0.5672.126-1.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-05-22 00:38:19 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Leon Fauster
2023-05-07 13:15:11 UTC
it looks like selinux policy issue. Please try following command as workarounds: setsebool -P unconfined_chrome_sandbox_transition 0 The denial interpreted: ---- type=PROCTITLE msg=audit(05/07/2023 09:05:24.510:7304) : proctitle=/usr/lib64/chromium-browser/chromium-browser --type=zygote --crashpad-handler-pid=68828 --enable-crash-reporter=,Fedora Project type=AVC msg=audit(05/07/2023 09:05:24.510:7304) : avc: denied { setcap } for pid=72523 comm=chromium-browse scontext=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 tclass=process permissive=0 type=SYSCALL msg=audit(05/07/2023 09:05:24.510:7304) : arch=x86_64 syscall=capset success=no exit=EACCES(Permission denied) a0=0x7ffd7da22980 a1=0x7ffd7da22960 a2=0x7f884b3818b8 a3=0x0 items=0 ppid=68845 pid=72523 auid=unknown(1200) uid=unknown(1200) gid=unknown(1200) euid=unknown(1200) suid=unknown(1200) fsuid=unknown(1200) egid=unknown(1200) sgid=unknown(1200) fsgid=unknown(1200) tty=(none) ses=34 comm=chromium-browse exe=/usr/lib64/chromium-browser/chromium-browser subj=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 key=(null) show capset(2) is being called. Is this a new feature? Would the following local module help? # cat local_chromesandbox_capset.cil (allow chrome_sandbox_t chrome_sandbox_t (process (setcap))) # semodule -i local_chromesandbox_capset.cil <reproduce> Hi Zdenek, yes, the capset system call is used in Chromium Sandbox. I have tried your local_chromesandbox_capset.cil and confirmed that the problem is fixed, Chromium works fine after that. Can we have it in selinux-policy? Thanks! I've submitted a Fedora PR to address the issue in F38 and newer: https://github.com/fedora-selinux/selinux-policy/pull/1679 FEDORA-EPEL-2023-1388277bf4 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-1388277bf4 FEDORA-EPEL-2023-2694488870 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2694488870 FEDORA-2023-5c477a04ca has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5c477a04ca FEDORA-EPEL-2023-6fba4b91e0 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-6fba4b91e0 FEDORA-2023-69264c19f9 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-69264c19f9 FEDORA-EPEL-2023-1388277bf4 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-1388277bf4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-2694488870 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2694488870 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-6fba4b91e0 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-6fba4b91e0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-69264c19f9 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-69264c19f9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-69264c19f9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-5c477a04ca has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-5c477a04ca` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5c477a04ca See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-69264c19f9 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-5c477a04ca has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2023-6fba4b91e0 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2023-1388277bf4 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2023-2694488870 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. |