https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-16T17:22:16.466278+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cve-2020-35915 CVE-2020-35915 2026-10-16T17:22:16.500608+00:00

An issue was discovered in the futures-intrusive crate before 0.4.0 for Rust. GenericMutexGuard allows cross-thread data races of non-Sync types.

 https://cve.radiocsirt.org/vuln/rustsec-2020-0072 RUSTSEC-2020-0072 — GenericMutexGuard allows data races of non-Sync types across threads 2026-10-16T17:22:16.500665+00:00

Affected: crates.io: futures-intrusive

`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.

This bug is [similar to one](https://github.com/rust-lang/rust/issues/41622) in `std::sync::Mutex`.