<?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-28T10:54:48.031641+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-64244</id>
    <title>CVE-2026-64244 — drivers/base/memory: set mem-&gt;altmap after successful device registration</title>
    <updated>2026-09-28T10:54:48.034624+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>drivers/base/memory: set mem-&gt;altmap after successful device registration</p>
<p>If __add_memory_block() fails at xa_store() (under memory pressure for
example), device_unregister() is called, which eventually triggers
memory_block_release() with mem-&gt;altmap still set, causing a
WARN_ON(mem-&gt;altmap).  This was triggered by modifying virtio-mem driver.</p>
<p>Fix this by delaying the assignment of mem-&gt;altmap until after
__add_memory_block() has succeeded.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-64244"/>
  </entry>
</feed>
