<?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>Wed, 07 Oct 2026 22:55:14 +0000</lastBuildDate>
    <item>
      <title>RUSTSEC-2025-0050 — IdMap::from_iter may lead to uninitialized memory being freed on drop</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2025-0050</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: id-map&lt;/p&gt;
&lt;p&gt;Due to a flaw in the constructor `id_map::IdMap::from_iter`, ill-formed objects may be created in which the amount of actually initialized memory is less than what is expected by the fields of `IdMap`. Specifically, the field `ids` is initialized based on the capacity of the vector `values`, which is constructed from the provided iterator. However, the length of this vector may be smaller than its capacity.&lt;/p&gt;
&lt;p&gt;In such cases, when the resulting `IdMap` is dropped, its destructor incorrectly assumes that `values` contains `ids.len() == values.capacity()` initialized elements and attempts to iterate over and drop them. This leads to dereferencing and attempting to free uninitialized memory, resulting in undefined behavior and potential segmentation faults.&lt;/p&gt;
&lt;p&gt;The bug was fixed in commit `fab6922`, and all unsafe code was removed from the crate.&lt;/p&gt;
&lt;p&gt;Note that the maintainer recommends using the following alternatives:
- [slab](https://crates.io/crates/slab)
- [slotmap](https://crates.io/crates/slotmap)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: id-map&lt;/p&gt;
&lt;p&gt;Due to a flaw in the constructor `id_map::IdMap::from_iter`, ill-formed objects may be created in which the amount of actually initialized memory is less than what is expected by the fields of `IdMap`. Specifically, the field `ids` is initialized based on the capacity of the vector `values`, which is constructed from the provided iterator. However, the length of this vector may be smaller than its capacity.&lt;/p&gt;
&lt;p&gt;In such cases, when the resulting `IdMap` is dropped, its destructor incorrectly assumes that `values` contains `ids.len() == values.capacity()` initialized elements and attempts to iterate over and drop them. This leads to dereferencing and attempting to free uninitialized memory, resulting in undefined behavior and potential segmentation faults.&lt;/p&gt;
&lt;p&gt;The bug was fixed in commit `fab6922`, and all unsafe code was removed from the crate.&lt;/p&gt;
&lt;p&gt;Note that the maintainer recommends using the following alternatives:
- [slab](https://crates.io/crates/slab)
- [slotmap](https://crates.io/crates/slotmap)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2025-0050</guid>
    </item>
  </channel>
</rss>
