<?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://vulnerability.circl.lu</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, 30 Sep 2026 08:25:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-46847 — mm: vmalloc: ensure vmap_block is initialised before adding to queue</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-46847</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: vmalloc: ensure vmap_block is initialised before adding to queue&lt;/p&gt;
&lt;p&gt;Commit 8c61291fd850 (&amp;#34;mm: fix incorrect vbq reference in
purge_fragmented_block&amp;#34;) extended the &amp;#39;vmap_block&amp;#39; structure to contain a
&amp;#39;cpu&amp;#39; field which is set at allocation time to the id of the initialising
CPU.&lt;/p&gt;
&lt;p&gt;When a new &amp;#39;vmap_block&amp;#39; is being instantiated by new_vmap_block(), the
partially initialised structure is added to the local &amp;#39;vmap_block_queue&amp;#39;
xarray before the &amp;#39;cpu&amp;#39; field has been initialised.  If another CPU is
concurrently walking the xarray (e.g.  via vm_unmap_aliases()), then it
may perform an out-of-bounds access to the remote queue thanks to an
uninitialised index.&lt;/p&gt;
&lt;p&gt;This has been observed as UBSAN errors in Android:&lt;/p&gt;
&lt;p&gt;| Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP
 |
 | Call trace:
 |  purge_fragmented_block+0x204/0x21c
 |  _vm_unmap_aliases+0x170/0x378
 |  vm_unmap_aliases+0x1c/0x28
 |  change_memory_common+0x1dc/0x26c
 |  set_memory_ro+0x18/0x24
 |  module_enable_ro+0x98/0x238
 |  do_init_module+0x1b0/0x310&lt;/p&gt;
&lt;p&gt;Move the initialisation of &amp;#39;vb-&amp;gt;cpu&amp;#39; in new_vmap_block() ahead of the
addition to the xarray.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: vmalloc: ensure vmap_block is initialised before adding to queue&lt;/p&gt;
&lt;p&gt;Commit 8c61291fd850 (&amp;#34;mm: fix incorrect vbq reference in
purge_fragmented_block&amp;#34;) extended the &amp;#39;vmap_block&amp;#39; structure to contain a
&amp;#39;cpu&amp;#39; field which is set at allocation time to the id of the initialising
CPU.&lt;/p&gt;
&lt;p&gt;When a new &amp;#39;vmap_block&amp;#39; is being instantiated by new_vmap_block(), the
partially initialised structure is added to the local &amp;#39;vmap_block_queue&amp;#39;
xarray before the &amp;#39;cpu&amp;#39; field has been initialised.  If another CPU is
concurrently walking the xarray (e.g.  via vm_unmap_aliases()), then it
may perform an out-of-bounds access to the remote queue thanks to an
uninitialised index.&lt;/p&gt;
&lt;p&gt;This has been observed as UBSAN errors in Android:&lt;/p&gt;
&lt;p&gt;| Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP
 |
 | Call trace:
 |  purge_fragmented_block+0x204/0x21c
 |  _vm_unmap_aliases+0x170/0x378
 |  vm_unmap_aliases+0x1c/0x28
 |  change_memory_common+0x1dc/0x26c
 |  set_memory_ro+0x18/0x24
 |  module_enable_ro+0x98/0x238
 |  do_init_module+0x1b0/0x310&lt;/p&gt;
&lt;p&gt;Move the initialisation of &amp;#39;vb-&amp;gt;cpu&amp;#39; in new_vmap_block() ahead of the
addition to the xarray.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-46847</guid>
    </item>
  </channel>
</rss>
