Bug 2483935

Summary: Remove setuid bit from chromium-browser's chrome-sandbox (now relies on namespaces)
Product: [Fedora] Fedora Reporter: Pierre PINON <pierre>
Component: chromiumAssignee: Than Ngo <than>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 43CC: pigpigman8686, spotrh, suraj.ghimire7, than, yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: chromium-149.0.7827.102-1.fc43 chromium-149.0.7827.102-1.fc44 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-06-13 00:56:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Pierre PINON 2026-06-02 10:03:05 UTC
The chrome-sandbox binary in the chromium-browser package currently retains the setuid bit, which is no longer strictly necessary. Upstream Chromium has transitioned to using Linux namespaces, seccomp-BPF, and user namespaces as the primary sandboxing mechanisms, reducing reliance on setuid. 

Reproducible: Always

Comment 1 Than Ngo 2026-06-02 10:28:28 UTC
The chrome-sandbox helper historically needed the setuid root bit so it could create a restricted sandbox for renderer processes. On modern Linux systems like fedora/rhel, Chromium prefers the user namespace sandbox, which does not require a setuid binary.

I will fix it in next build. Thanks for you report!

Comment 2 Fedora Update System 2026-06-11 14:50:26 UTC
FEDORA-2026-2debc85b3c (chromium-149.0.7827.102-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-2debc85b3c

Comment 3 Fedora Update System 2026-06-11 14:50:26 UTC
FEDORA-2026-c5c0986fb6 (chromium-149.0.7827.102-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-c5c0986fb6

Comment 4 Fedora Update System 2026-06-12 01:30:26 UTC
FEDORA-2026-2debc85b3c has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-2debc85b3c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-2debc85b3c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-06-12 01:51:52 UTC
FEDORA-2026-c5c0986fb6 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-c5c0986fb6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-c5c0986fb6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-06-13 00:56:25 UTC
FEDORA-2026-c5c0986fb6 (chromium-149.0.7827.102-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2026-06-13 01:12:01 UTC
FEDORA-2026-2debc85b3c (chromium-149.0.7827.102-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2026-06-14 05:03:42 UTC
FEDORA-2026-c5c0986fb6 (chromium-149.0.7827.102-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.