<?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>Thu, 15 Oct 2026 21:14:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-36446</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2020-36446</link>
      <description>&lt;p&gt;An issue was discovered in the signal-simple crate through 2020-11-15 for Rust. There are unconditional implementations of Send and Sync for SyncChannel&amp;lt;T&amp;gt;.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in the signal-simple crate through 2020-11-15 for Rust. There are unconditional implementations of Send and Sync for SyncChannel&amp;lt;T&amp;gt;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2020-36446</guid>
    </item>
    <item>
      <title>RUSTSEC-2020-0126 — SyncChannel&lt;T&gt; can move 'T: !Send' to other threads</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2020-0126</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: signal-simple&lt;/p&gt;
&lt;p&gt;Affected versions of this crate unconditionally implement Send/Sync for `SyncChannel&amp;lt;T&amp;gt;`.
`SyncChannel&amp;lt;T&amp;gt;` doesn&amp;#39;t provide access to `&amp;amp;T` but merely serves as a channel that consumes and returns owned `T`.&lt;/p&gt;
&lt;p&gt;Users can create UB in safe Rust by sending `T: !Send` to other threads with `SyncChannel::send/recv` APIs. Using `T = Arc&amp;lt;Cell&amp;lt;_&amp;gt;` allows to create data races (which can lead to memory corruption), and using `T = MutexGuard&amp;lt;T&amp;gt;` allows to unlock a mutex from a thread that didn&amp;#39;t lock the mutex.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: signal-simple&lt;/p&gt;
&lt;p&gt;Affected versions of this crate unconditionally implement Send/Sync for `SyncChannel&amp;lt;T&amp;gt;`.
`SyncChannel&amp;lt;T&amp;gt;` doesn&amp;#39;t provide access to `&amp;amp;T` but merely serves as a channel that consumes and returns owned `T`.&lt;/p&gt;
&lt;p&gt;Users can create UB in safe Rust by sending `T: !Send` to other threads with `SyncChannel::send/recv` APIs. Using `T = Arc&amp;lt;Cell&amp;lt;_&amp;gt;` allows to create data races (which can lead to memory corruption), and using `T = MutexGuard&amp;lt;T&amp;gt;` allows to unlock a mutex from a thread that didn&amp;#39;t lock the mutex.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2020-0126</guid>
    </item>
  </channel>
</rss>
