https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 16 Oct 2026 14:00:36 +0000 https://cve.radiocsirt.org/vuln/cnvd-2021-39557 cnvd-2021-39557 https://cve.radiocsirt.org/vuln/cnvd-2021-39557 https://cve.radiocsirt.org/vuln/euvd-2026-47907 EUVD-2026-47907 https://cve.radiocsirt.org/vuln/euvd-2026-47907 https://cve.radiocsirt.org/vuln/fkie_cve-2020-35915 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-35915 https://cve.radiocsirt.org/vuln/ghsa-4hjg-cx88-g9f9 <p><strong>Affected:</strong> crates.io: futures-intrusive</p> <p>GenericMutexGuard&lt;T&gt; 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.</p> <p>This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code.</p> <p>The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard&#39;s Sync trait.</p> <p><strong>Affected:</strong> crates.io: futures-intrusive</p> <p>GenericMutexGuard&lt;T&gt; 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.</p> <p>This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code.</p> <p>The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard&#39;s Sync trait.</p> https://cve.radiocsirt.org/vuln/ghsa-4hjg-cx88-g9f9 https://cve.radiocsirt.org/vuln/gsd-2020-35915 gsd-2020-35915 https://cve.radiocsirt.org/vuln/gsd-2020-35915 https://cve.radiocsirt.org/vuln/rustsec-2020-0072 <p><strong>Affected:</strong> crates.io: futures-intrusive</p> <p>`GenericMutexGuard&lt;T&gt;` 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.</p> <p>This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code.</p> <p>The flaw was corrected by adding a `T: Send + Sync` bound for `GenericMutexGuard`&#39;s `Sync` trait.</p> <p>This bug is [similar to one](https://github.com/rust-lang/rust/issues/41622) in `std::sync::Mutex`.</p> <p><strong>Affected:</strong> crates.io: futures-intrusive</p> <p>`GenericMutexGuard&lt;T&gt;` 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.</p> <p>This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code.</p> <p>The flaw was corrected by adding a `T: Send + Sync` bound for `GenericMutexGuard`&#39;s `Sync` trait.</p> <p>This bug is [similar to one](https://github.com/rust-lang/rust/issues/41622) in `std::sync::Mutex`.</p> https://cve.radiocsirt.org/vuln/rustsec-2020-0072