<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T03:37:38.595411+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-64180</id>
    <title>CVE-2026-64180 — mm/memory_hotplug: fix memory block reference leak on remove</title>
    <updated>2026-09-30T03:37:38.608176+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mm/memory_hotplug: fix memory block reference leak on remove</p>
<p>Patch series "mm: Fix memory block leaks and locking", v2.</p>
<p>This series fixes two memory block device reference leaks and one locking
issue around the per-memory_block hwpoison counter.</p>
<p>This patch (of 2):</p>
<p>remove_memory_blocks_and_altmaps() looks up each memory block with
find_memory_block(), which acquires a reference to the memory block
device.</p>
<p>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-&gt;altmap and clearing mem-&gt;altmap, before
removing the memory block device.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-64180"/>
  </entry>
</feed>
