<?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://db.gcve.eu</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, 16 Nov 2026 01:10:45 +0000</lastBuildDate>
    <item>
      <title>RUSTSEC-2024-0005 — Unsound sending of non-Send types across threads</title>
      <link>https://db.gcve.eu/vuln/rustsec-2024-0005</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: threadalone&lt;/p&gt;
&lt;p&gt;Affected versions can run the `Drop` impl of a non-Send type on a different
thread than it was created on.&lt;/p&gt;
&lt;p&gt;The flaw occurs when a stderr write performed by the `threadalone` crate fails,
for example because stderr is redirected to a location on a filesystem that is
full, or because stderr is a pipe that has been closed by the reader.&lt;/p&gt;
&lt;p&gt;Dropping a non-Send type on the wrong thread is unsound. If used with a type
such as a pthread-based `MutexGuard`, [the consequence is undefined
behavior][mutexguard]. If used with `Rc`, there would be a data race on the
reference count, which is likewise undefined behavior.&lt;/p&gt;
&lt;p&gt;[mutexguard]: https://github.com/rust-lang/rust/issues/23465#issuecomment-82730326&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: threadalone&lt;/p&gt;
&lt;p&gt;Affected versions can run the `Drop` impl of a non-Send type on a different
thread than it was created on.&lt;/p&gt;
&lt;p&gt;The flaw occurs when a stderr write performed by the `threadalone` crate fails,
for example because stderr is redirected to a location on a filesystem that is
full, or because stderr is a pipe that has been closed by the reader.&lt;/p&gt;
&lt;p&gt;Dropping a non-Send type on the wrong thread is unsound. If used with a type
such as a pthread-based `MutexGuard`, [the consequence is undefined
behavior][mutexguard]. If used with `Rc`, there would be a data race on the
reference count, which is likewise undefined behavior.&lt;/p&gt;
&lt;p&gt;[mutexguard]: https://github.com/rust-lang/rust/issues/23465#issuecomment-82730326&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rustsec-2024-0005</guid>
    </item>
  </channel>
</rss>
