MEDIUM5.5
GHSA-4hjg-cx88-g9f9
Data races in futures-intrusive
Details
GenericMutexGuard<T> was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is.
This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code.
The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait.
Are you affected?
Enter the version of the package you're using.
Affected packages
crates.io/futures-intrusive
Introduced in:
0Fixed in: 0.4.0Upgrade futures-intrusive to 0.4.0 or newer (ecosystem crates.io).