Bug 2366580 - CVE-2025-4574 tuigreet: crossbeam-channel Vulnerable to Double Free on Drop [fedora-42]
Summary: CVE-2025-4574 tuigreet: crossbeam-channel Vulnerable to Double Free on Drop [...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tuigreet
Version: 42
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Aleksei Bavshin
QA Contact:
URL:
Whiteboard: {"flaws": ["62aa5787-67fa-449e-acc0-a...
Depends On:
Blocks: CVE-2025-4574, GHSA-pg9f-39pc-qf8g
TreeView+ depends on / blocked
 
Reported: 2025-05-15 14:36 UTC by Michal Findra
Modified: 2025-09-12 19:27 UTC (History)
2 users (show)

Fixed In Version: tuigreet-0.9.1-4.fc42 tuigreet-0.9.1-4.fc41 tuigreet-0.9.1-4.fc43
Clone Of:
Environment:
Last Closed: 2025-09-11 00:55:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal Findra 2025-05-15 14:36:44 UTC
More information about this security flaw is available in the following bug:

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

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-09-02 20:41:17 UTC
FEDORA-2025-ff79e403f1 (tuigreet-0.9.1-4.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-ff79e403f1

Comment 2 Fedora Update System 2025-09-02 20:41:17 UTC
FEDORA-2025-369dc8a50e (tuigreet-0.9.1-4.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-369dc8a50e

Comment 3 Fedora Update System 2025-09-02 20:41:17 UTC
FEDORA-2025-df23dd806a (tuigreet-0.9.1-4.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-df23dd806a

Comment 4 Fedora Update System 2025-09-03 00:51:47 UTC
FEDORA-2025-369dc8a50e 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-369dc8a50e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-369dc8a50e

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

Comment 5 Fedora Update System 2025-09-03 01:14:52 UTC
FEDORA-2025-df23dd806a 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-df23dd806a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-df23dd806a

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

Comment 6 Fedora Update System 2025-09-03 01:32:18 UTC
FEDORA-2025-ff79e403f1 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-ff79e403f1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ff79e403f1

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

Comment 7 Fedora Update System 2025-09-11 00:55:49 UTC
FEDORA-2025-369dc8a50e (tuigreet-0.9.1-4.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-09-11 01:19:41 UTC
FEDORA-2025-ff79e403f1 (tuigreet-0.9.1-4.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-09-12 19:27:51 UTC
FEDORA-2025-df23dd806a (tuigreet-0.9.1-4.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.