<?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 22:08:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46280 — lib: test_hmm: evict device pages on file close to avoid use-after-free</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46280</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;lib: test_hmm: evict device pages on file close to avoid use-after-free&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;Minor hmm_test fixes and cleanups&amp;#34;.&lt;/p&gt;
&lt;p&gt;Two bugfixes a cleanup for the HMM kernel selftests.  These were mostly
reported by Zenghui Yu with special thanks to Lorenzo for analysing and
pointing out the problems.&lt;/p&gt;
&lt;p&gt;This patch (of 3):&lt;/p&gt;
&lt;p&gt;When dmirror_fops_release() is called it frees the dmirror struct but
doesn&amp;#39;t migrate device private pages back to system memory first.  This
leaves those pages with a dangling zone_device_data pointer to the freed
dmirror.&lt;/p&gt;
&lt;p&gt;If a subsequent fault occurs on those pages (eg.  during coredump) the
dmirror_devmem_fault() callback dereferences the stale pointer causing a
kernel panic.  This was reported [1] when running mm/ksft_hmm.sh on arm64,
where a test failure triggered SIGABRT and the resulting coredump walked
the VMAs faulting in the stale device private pages.&lt;/p&gt;
&lt;p&gt;Fix this by calling dmirror_device_evict_chunk() for each devmem chunk in
dmirror_fops_release() to migrate all device private pages back to system
memory before freeing the dmirror struct.  The function is moved earlier
in the file to avoid a forward declaration.&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;lib: test_hmm: evict device pages on file close to avoid use-after-free&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;Minor hmm_test fixes and cleanups&amp;#34;.&lt;/p&gt;
&lt;p&gt;Two bugfixes a cleanup for the HMM kernel selftests.  These were mostly
reported by Zenghui Yu with special thanks to Lorenzo for analysing and
pointing out the problems.&lt;/p&gt;
&lt;p&gt;This patch (of 3):&lt;/p&gt;
&lt;p&gt;When dmirror_fops_release() is called it frees the dmirror struct but
doesn&amp;#39;t migrate device private pages back to system memory first.  This
leaves those pages with a dangling zone_device_data pointer to the freed
dmirror.&lt;/p&gt;
&lt;p&gt;If a subsequent fault occurs on those pages (eg.  during coredump) the
dmirror_devmem_fault() callback dereferences the stale pointer causing a
kernel panic.  This was reported [1] when running mm/ksft_hmm.sh on arm64,
where a test failure triggered SIGABRT and the resulting coredump walked
the VMAs faulting in the stale device private pages.&lt;/p&gt;
&lt;p&gt;Fix this by calling dmirror_device_evict_chunk() for each devmem chunk in
dmirror_fops_release() to migrate all device private pages back to system
memory before freeing the dmirror struct.  The function is moved earlier
in the file to avoid a forward declaration.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-46280</guid>
    </item>
  </channel>
</rss>
