<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 16 Oct 2026 19:18:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-35915</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2020-35915</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2020-35915</guid>
    </item>
    <item>
      <title>RUSTSEC-2020-0072 — GenericMutexGuard allows data races of non-Sync types across threads</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2020-0072</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: futures-intrusive&lt;/p&gt;
&lt;p&gt;`GenericMutexGuard&amp;lt;T&amp;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.&lt;/p&gt;
&lt;p&gt;This is a soundness issue and allows data races, potentially leading to crashes
and segfaults from safe Rust code.&lt;/p&gt;
&lt;p&gt;The flaw was corrected by adding a `T: Send + Sync` bound for
`GenericMutexGuard`&amp;#39;s `Sync` trait.&lt;/p&gt;
&lt;p&gt;This bug is [similar to one](https://github.com/rust-lang/rust/issues/41622) in
`std::sync::Mutex`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: futures-intrusive&lt;/p&gt;
&lt;p&gt;`GenericMutexGuard&amp;lt;T&amp;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.&lt;/p&gt;
&lt;p&gt;This is a soundness issue and allows data races, potentially leading to crashes
and segfaults from safe Rust code.&lt;/p&gt;
&lt;p&gt;The flaw was corrected by adding a `T: Send + Sync` bound for
`GenericMutexGuard`&amp;#39;s `Sync` trait.&lt;/p&gt;
&lt;p&gt;This bug is [similar to one](https://github.com/rust-lang/rust/issues/41622) in
`std::sync::Mutex`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2020-0072</guid>
    </item>
  </channel>
</rss>
