<?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>Sat, 17 Oct 2026 21:10:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-36436</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2020-36436</link>
      <description>&lt;p&gt;An issue was discovered in the unicycle crate before 0.7.1 for Rust. PinSlab&amp;lt;T&amp;gt; and Unordered&amp;lt;T, S&amp;gt; do not have bounds on their Send and Sync traits.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in the unicycle crate before 0.7.1 for Rust. PinSlab&amp;lt;T&amp;gt; and Unordered&amp;lt;T, S&amp;gt; do not have bounds on their Send and Sync traits.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2020-36436</guid>
    </item>
    <item>
      <title>RUSTSEC-2020-0116 — PinSlab&lt;T&gt; and Unordered&lt;T, S&gt; need bounds on their Send/Sync traits</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2020-0116</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: unicycle&lt;/p&gt;
&lt;p&gt;Affected versions of this crate unconditionally implemented `Send` &amp;amp; `Sync` for types `PinSlab&amp;lt;T&amp;gt;` &amp;amp; `Unordered&amp;lt;T, S&amp;gt;`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.&lt;/p&gt;
&lt;p&gt;This can result in a data race &amp;amp; memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab&amp;lt;T&amp;gt;` or `Unordered&amp;lt;T, S&amp;gt;` and accessed concurrently from multiple threads.&lt;/p&gt;
&lt;p&gt;The flaw was corrected in commits 92f40b4 &amp;amp; 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab&amp;lt;T&amp;gt;` &amp;amp; `Unordered&amp;lt;T, S&amp;gt;` and adding `T: Sync` to `Sync` impls for `PinSlab&amp;lt;T&amp;gt;` &amp;amp; `Unordered&amp;lt;T, S&amp;gt;`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: unicycle&lt;/p&gt;
&lt;p&gt;Affected versions of this crate unconditionally implemented `Send` &amp;amp; `Sync` for types `PinSlab&amp;lt;T&amp;gt;` &amp;amp; `Unordered&amp;lt;T, S&amp;gt;`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.&lt;/p&gt;
&lt;p&gt;This can result in a data race &amp;amp; memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab&amp;lt;T&amp;gt;` or `Unordered&amp;lt;T, S&amp;gt;` and accessed concurrently from multiple threads.&lt;/p&gt;
&lt;p&gt;The flaw was corrected in commits 92f40b4 &amp;amp; 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab&amp;lt;T&amp;gt;` &amp;amp; `Unordered&amp;lt;T, S&amp;gt;` and adding `T: Sync` to `Sync` impls for `PinSlab&amp;lt;T&amp;gt;` &amp;amp; `Unordered&amp;lt;T, S&amp;gt;`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2020-0116</guid>
    </item>
  </channel>
</rss>
