Bug 2399082

Summary: CVE-2025-47906 docker-buildx: Unexpected paths returned from LookPath in os/exec [fedora-41]
Product: [Fedora] Fedora Reporter: Jon Moroney <jmoroney>
Component: docker-buildxAssignee: Maxwell G <maxwell>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 41CC: bradley.g.smith, go-sig, maxwell
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["82b592f6-3fef-4109-80a1-8023edc09049"]}
Fixed In Version: docker-buildx-0.29.0-1.fc44 docker-buildx-0.29.1-1.fc41 docker-buildx-0.29.1-1.fc42 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-10-01 15:56:14 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:
Bug Depends On:    
Bug Blocks: 2396546    

Description Jon Moroney 2025-09-25 23:57:17 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams

Comment 1 Fedora Update System 2025-10-01 15:50:52 UTC
FEDORA-2025-05a723591b (docker-buildx-0.29.0-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-05a723591b

Comment 2 Fedora Update System 2025-10-01 15:56:14 UTC
FEDORA-2025-05a723591b (docker-buildx-0.29.0-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 3 Fedora Update System 2025-10-01 16:33:24 UTC
FEDORA-2025-c1845a0227 (docker-buildx-0.29.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-c1845a0227

Comment 4 Fedora Update System 2025-10-01 16:48:29 UTC
FEDORA-2025-72c032a36f (docker-buildx-0.29.0-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-72c032a36f

Comment 5 Fedora Update System 2025-10-01 17:00:35 UTC
FEDORA-2025-7305de85ef (docker-buildx-0.29.0-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-7305de85ef

Comment 6 Fedora Update System 2025-10-02 00:54:37 UTC
FEDORA-2025-72c032a36f has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-72c032a36f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-72c032a36f

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

Comment 7 Fedora Update System 2025-10-02 01:10:37 UTC
FEDORA-2025-c1845a0227 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-2025-c1845a0227`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c1845a0227

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

Comment 8 Fedora Update System 2025-10-02 01:30:37 UTC
FEDORA-2025-7305de85ef has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-7305de85ef`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-7305de85ef

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

Comment 9 Fedora Update System 2025-10-04 01:39:20 UTC
FEDORA-2025-455aa01b65 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-455aa01b65`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-455aa01b65

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

Comment 10 Fedora Update System 2025-10-04 01:55:01 UTC
FEDORA-2025-d81c797483 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-2025-d81c797483`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d81c797483

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

Comment 11 Fedora Update System 2025-10-04 02:15:32 UTC
FEDORA-2025-0aaef4df82 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-0aaef4df82`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-0aaef4df82

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

Comment 12 Fedora Update System 2025-10-12 01:10:18 UTC
FEDORA-2025-455aa01b65 (docker-buildx-0.29.1-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2025-10-12 01:23:32 UTC
FEDORA-2025-0aaef4df82 (docker-buildx-0.29.1-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.