crossbeam-channel
Affected
- introduced
0.5.12-0, fixed0.5.15(semver)
Fixed versions
0.5.15
Fix
- Fixed version
0.5.15cargo update -p crossbeam-channel --precise 0.5.15
Advisory
Also known as: CVE-2025-4574, GHSA-pg9f-39pc-qf8g, TROVE-2025-013
crossbeam-channel: double free on Drop
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:
> 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,
first published in 0.5.12.
The fix is in
upstream MR \#1187
and has been published in 0.5.15
Not rated by the source.
0.5.12-0, fixed 0.5.15 (semver)0.5.15
0.5.15cargo update -p crossbeam-channel --precise 0.5.15Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0