Skip to content

RUSTSEC-2025-0024: crossbeam-channel: double free on Drop #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
github-actions bot opened this issue Apr 14, 2025 · 0 comments
Open

RUSTSEC-2025-0024: crossbeam-channel: double free on Drop #25

github-actions bot opened this issue Apr 14, 2025 · 0 comments

Comments

@github-actions
Copy link

crossbeam-channel: double free on Drop

Details
Package crossbeam-channel
Version 0.5.14
URL crossbeam-rs/crossbeam#1187
Date 2025-04-08
Patched versions >=0.5.15
Unaffected versions <=0.5.11

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

See advisory page for additional details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants