RUSTSEC-2025-0024

See a problem?
Please try reporting it to the source first.

Source

https://rustsec.org/advisories/RUSTSEC-2025-0024

Import Source

https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2025-0024.json

JSON Data

https://api.osv.dev/v1/vulns/RUSTSEC-2025-0024

Aliases

Published

2025-04-08T12:00:00Z

Modified

2025-10-28T06:29:00.070713Z

Summary

crossbeam-channel: double free on Drop

Details

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

Database specific

{
    "license": "CC0-1.0"
}

References

Affected packages

crates.io / crossbeam-channel

Package

Name: crossbeam-channel; View open source insights on deps.dev
Purl: pkg:cargo/crossbeam-channel

Affected ranges

Type: SEMVER
Events: Introduced

0.5.12-0

Fixed

0.5.15

Ecosystem specific

{
    "affected_functions": null,
    "affects": {
        "os": [],
        "functions": [],
        "arch": []
    }
}

Database specific

cvss

null

informational

null