<?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>Thu, 01 Oct 2026 19:53:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46281 — vmalloc: fix buffer overflow in vrealloc_node_align()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46281</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;vmalloc: fix buffer overflow in vrealloc_node_align()&lt;/p&gt;
&lt;p&gt;Commit 4c5d3365882d (&amp;#34;mm/vmalloc: allow to set node and align in
vrealloc&amp;#34;) added the ability to force a new allocation if the current
pointer is on the wrong NUMA node, or if an alignment constraint is not
met, even if the user is shrinking the allocation.&lt;/p&gt;
&lt;p&gt;On this path (need_realloc), the code allocates a new object of &amp;#39;size&amp;#39;
bytes and then memcpy()s &amp;#39;old_size&amp;#39; bytes into it.  If the request is to
shrink the object (size &amp;lt; old_size), this results in an out-of-bounds
write on the new buffer.&lt;/p&gt;
&lt;p&gt;Fix this by bounding the copy length by the new allocation size.&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;vmalloc: fix buffer overflow in vrealloc_node_align()&lt;/p&gt;
&lt;p&gt;Commit 4c5d3365882d (&amp;#34;mm/vmalloc: allow to set node and align in
vrealloc&amp;#34;) added the ability to force a new allocation if the current
pointer is on the wrong NUMA node, or if an alignment constraint is not
met, even if the user is shrinking the allocation.&lt;/p&gt;
&lt;p&gt;On this path (need_realloc), the code allocates a new object of &amp;#39;size&amp;#39;
bytes and then memcpy()s &amp;#39;old_size&amp;#39; bytes into it.  If the request is to
shrink the object (size &amp;lt; old_size), this results in an out-of-bounds
write on the new buffer.&lt;/p&gt;
&lt;p&gt;Fix this by bounding the copy length by the new allocation size.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-46281</guid>
    </item>
  </channel>
</rss>
