Most recent entries from all

cnvd-2021-39557

2026-10-16T16:56:23.758761+00:00

cnvd-2021-39557

EUVD-2026-47907

2026-10-16T16:56:23.758795+00:00

EUVD-2026-47907

fkie_cve-2020-35915

2026-10-16T16:56:23.758809+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.

GHSA-4hjg-cx88-g9f9 — Data races in futures-intrusive

2026-10-16T16:56:23.758835+00:00

Affected: crates.io: futures-intrusive

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

gsd-2020-35915

2026-10-16T16:56:23.758863+00:00

gsd-2020-35915

RUSTSEC-2020-0072 — GenericMutexGuard allows data races of non-Sync types across threads

2026-10-16T16:56:23.758874+00:00

Affected: crates.io: futures-intrusive

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