Bug 2350799

Summary: CVE-2025-22869 podman-tui: Denial of Service in the Key Exchange of golang.org/x/crypto/ssh [fedora-40]
Product: [Fedora] Fedora Reporter: Anten Skrabec <askrabec>
Component: podman-tuiAssignee: Navid Yaghoobi <n.yaghoobi.s>
Status: CLOSED ERRATA QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 40CC: go-sig, n.yaghoobi.s
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["9f978159-dda3-482c-997c-330bc6def185"]}
Fixed In Version: podman-tui-1.5.0-1.fc42 podman-tui-1.5.0-1.fc41 podman-tui-1.5.0-1.el10_1 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-04-15 17:59:13 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: 2348367    

Description Anten Skrabec 2025-03-08 01:15:26 UTC
More information about this security flaw is available in the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=2348367

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.

Comment 1 Fedora Update System 2025-04-06 06:50:10 UTC
FEDORA-2025-f1d2ae375e (podman-tui-1.5.0-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f1d2ae375e

Comment 2 Fedora Update System 2025-04-06 06:50:10 UTC
FEDORA-EPEL-2025-6618927fc5 (podman-tui-1.5.0-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-6618927fc5

Comment 3 Fedora Update System 2025-04-06 06:50:11 UTC
FEDORA-2025-8a7d23116e (podman-tui-1.5.0-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-8a7d23116e

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

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

Comment 5 Fedora Update System 2025-04-07 01:37:32 UTC
FEDORA-EPEL-2025-6618927fc5 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-6618927fc5

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

Comment 6 Fedora Update System 2025-04-07 02:11:45 UTC
FEDORA-2025-8a7d23116e 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-8a7d23116e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-8a7d23116e

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

Comment 7 Fedora Update System 2025-04-15 17:59:13 UTC
FEDORA-2025-8a7d23116e (podman-tui-1.5.0-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-04-15 18:34:30 UTC
FEDORA-2025-f1d2ae375e (podman-tui-1.5.0-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 9 Fedora Update System 2025-04-15 18:52:14 UTC
FEDORA-EPEL-2025-6618927fc5 (podman-tui-1.5.0-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.