<?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>Mon, 19 Oct 2026 23:22:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-36458</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2020-36458</link>
      <description>&lt;p&gt;An issue was discovered in the lexer crate through 2020-11-10 for Rust. For ReaderResult&amp;lt;T, E&amp;gt;, there is an implementation of Sync with a trait bound of T: Send, E: Send.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in the lexer crate through 2020-11-10 for Rust. For ReaderResult&amp;lt;T, E&amp;gt;, there is an implementation of Sync with a trait bound of T: Send, E: Send.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2020-36458</guid>
    </item>
    <item>
      <title>RUSTSEC-2020-0138 — ReaderResult should be bounded by Sync</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2020-0138</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: lexer&lt;/p&gt;
&lt;p&gt;Affected versions of this crate implements `Sync` for `ReaderResult&amp;lt;T, E&amp;gt;` with the trait bound `T: Send, E: Send`.&lt;/p&gt;
&lt;p&gt;Since matching on the public enum `ReaderResult&amp;lt;T, E&amp;gt;` provides access to `&amp;amp;T` &amp;amp; `&amp;amp;E`,
allowing data race to a non-Sync type `T` or `E`.
This can result in a memory corruption when multiple threads concurrently access `&amp;amp;T` or `&amp;amp;E`.&lt;/p&gt;
&lt;p&gt;Suggested fix for the bug is change the trait bounds imposed on `T` &amp;amp; `E` to be `T: Sync, E: Sync`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: lexer&lt;/p&gt;
&lt;p&gt;Affected versions of this crate implements `Sync` for `ReaderResult&amp;lt;T, E&amp;gt;` with the trait bound `T: Send, E: Send`.&lt;/p&gt;
&lt;p&gt;Since matching on the public enum `ReaderResult&amp;lt;T, E&amp;gt;` provides access to `&amp;amp;T` &amp;amp; `&amp;amp;E`,
allowing data race to a non-Sync type `T` or `E`.
This can result in a memory corruption when multiple threads concurrently access `&amp;amp;T` or `&amp;amp;E`.&lt;/p&gt;
&lt;p&gt;Suggested fix for the bug is change the trait bounds imposed on `T` &amp;amp; `E` to be `T: Sync, E: Sync`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2020-0138</guid>
    </item>
  </channel>
</rss>
