<?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, 08 Oct 2026 12:44:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-36086 — linked_list_allocator vulnerable to out-of-bound writes on `Heap` initialization and `Heap::extend`</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-36086</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rust-osdev linked-list-allocator&lt;/p&gt;
&lt;p&gt;linked_list_allocator is an allocator usable for no_std systems. Prior to version 0.10.2, the heap initialization methods were missing a minimum size check for the given heap size argument. This could lead to out-of-bound writes when a heap was initialized with a size smaller than `3 * size_of::&amp;lt;usize&amp;gt;` because of metadata write operations. This vulnerability impacts all the initialization functions on the `Heap` and `LockedHeap` types, including `Heap::new`, `Heap::init`, `Heap::init_from_slice`, and `LockedHeap::new`. It also affects multiple uses of the `Heap::extend` method. Version 0.10.2 contains a patch for the issue. As a workaround, ensure that the heap is only initialized with a size larger than `3 * size_of::&amp;lt;usize&amp;gt;` and that the `Heap::extend` method is only called with sizes larger than `2 * size_of::&amp;lt;usize&amp;gt;()`. Also, ensure that the total heap size is (and stays) a multiple of `2 * size_of::&amp;lt;usize&amp;gt;()`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rust-osdev linked-list-allocator&lt;/p&gt;
&lt;p&gt;linked_list_allocator is an allocator usable for no_std systems. Prior to version 0.10.2, the heap initialization methods were missing a minimum size check for the given heap size argument. This could lead to out-of-bound writes when a heap was initialized with a size smaller than `3 * size_of::&amp;lt;usize&amp;gt;` because of metadata write operations. This vulnerability impacts all the initialization functions on the `Heap` and `LockedHeap` types, including `Heap::new`, `Heap::init`, `Heap::init_from_slice`, and `LockedHeap::new`. It also affects multiple uses of the `Heap::extend` method. Version 0.10.2 contains a patch for the issue. As a workaround, ensure that the heap is only initialized with a size larger than `3 * size_of::&amp;lt;usize&amp;gt;` and that the `Heap::extend` method is only called with sizes larger than `2 * size_of::&amp;lt;usize&amp;gt;()`. Also, ensure that the total heap size is (and stays) a multiple of `2 * size_of::&amp;lt;usize&amp;gt;()`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-36086</guid>
    </item>
  </channel>
</rss>
