<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-12T18:57:59.366227+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2020-36206</id>
    <title>CVE-2020-36206</title>
    <updated>2026-10-12T18:57:59.398991+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in the rusb crate before 0.7.0 for Rust. Because of a lack of Send and Sync bounds, a data race and memory corruption can occur.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2020-36206"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rustsec-2020-0098</id>
    <title>RUSTSEC-2020-0098 — UsbContext trait did not require implementers to be Send and Sync.</title>
    <updated>2026-10-12T18:57:59.399037+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: rusb</p>
<p>Affected versions of `rusb` did not require `UsbContext` to implement `Send`
and `Sync`. However, through `Device` and `DeviceHandle` it is possible to use
`UsbContext`s across threads.</p>
<p>This issue allows non-thread safe `UsbContext` types to be used concurrently
leading to data races and memory corruption.</p>
<p>The issue was fixed by adding `Send` and `Sync` bounds to `UsbContext`.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rustsec-2020-0098"/>
  </entry>
</feed>
