<?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 13:56:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64180 — mm/memory_hotplug: fix memory block reference leak on remove</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64180</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/memory_hotplug: fix memory block reference leak on remove&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm: Fix memory block leaks and locking&amp;#34;, v2.&lt;/p&gt;
&lt;p&gt;This series fixes two memory block device reference leaks and one locking
issue around the per-memory_block hwpoison counter.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;remove_memory_blocks_and_altmaps() looks up each memory block with
find_memory_block(), which acquires a reference to the memory block
device.&lt;/p&gt;
&lt;p&gt;That reference is never dropped on this path, resulting in a leaked device
reference when removing memory blocks and their altmaps.  Drop the
reference after retrieving mem-&amp;gt;altmap and clearing mem-&amp;gt;altmap, before
removing the memory block device.&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/memory_hotplug: fix memory block reference leak on remove&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm: Fix memory block leaks and locking&amp;#34;, v2.&lt;/p&gt;
&lt;p&gt;This series fixes two memory block device reference leaks and one locking
issue around the per-memory_block hwpoison counter.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;remove_memory_blocks_and_altmaps() looks up each memory block with
find_memory_block(), which acquires a reference to the memory block
device.&lt;/p&gt;
&lt;p&gt;That reference is never dropped on this path, resulting in a leaked device
reference when removing memory blocks and their altmaps.  Drop the
reference after retrieving mem-&amp;gt;altmap and clearing mem-&amp;gt;altmap, before
removing the memory block device.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64180</guid>
    </item>
  </channel>
</rss>
