Most recent entries from all

CLEANSTART-2025-KZ08626 — Security fix for ghsa-pg9f-39pc-qf8g applied in: ztunnel-fips 1.25.5-r0

Affected: CleanStart: ztunnel-fips

Security vulnerability affects the ztunnel-fips package. This issue is resolved in later releases. See references for vulnerability details.

CVE-2025-4574 — Crossbeam-channel: crossbeam-channel vulnerable to double free on drop

Affected: crossbeam-channel, Red Hat Directory Server 11, Red Hat Directory Server 12, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat OpenShift AI (RHOAI), Red Hat OpenShift Container Platform 4, Red Hat Satellite 6 and 2 more

In crossbeam-channel rust crate, the internal `Channel` type's `Drop` method has a race condition which could, in some circumstances, lead to a double-free that could result in memory corruption.

RUSTSEC-2025-0024 — crossbeam-channel: double free on Drop

Affected: crates.io: crossbeam-channel

The internal `Channel` type's `Drop` method has a race which could, in some circumstances, lead to a double-free. This could result in memory corruption.

Quoting from the [upstream description in merge request \#1187](https://github.com/crossbeam-rs/crossbeam/pull/1187#issue-2980761131):

> The problem lies in the fact that `dicard_all_messages` contained two paths that could lead to `head.block` being read but only one of them would swap the value. This meant that `dicard_all_messages` could end up observing a non-null block pointer (and therefore attempting to free it) without setting `head.block` to null. This would then lead to `Channel::drop` making a second attempt at dropping the same pointer.

The bug was introduced while fixing a memory leak, in upstream [MR \#1084](https://github.com/crossbeam-rs/crossbeam/pull/1084), first published in 0.5.12.

The fix is in upstream [MR \#1187](https://github.com/crossbeam-rs/crossbeam/pull/1187) and has been published in 0.5.15