<?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-10-04T01:54:06.623474+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-46013</id>
    <title>CVE-2026-46013 — mm/memfd_luo: fix physical address conversion in put_folios cleanup</title>
    <updated>2026-10-04T01:54:06.652516+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/memfd_luo: fix physical address conversion in put_folios cleanup</p>
<p>In memfd_luo_retrieve_folios()'s put_folios cleanup path:</p>
<p>1. kho_restore_folio() expects a phys_addr_t (physical address) but
   receives a raw PFN (pfolio-&gt;pfn). This causes kho_restore_page() to
   check the wrong physical address (pfn &lt;&lt; PAGE_SHIFT instead of the
   actual physical address).</p>
<p>2. This loop lacks the !pfolio-&gt;pfn check that exists in the main
   retrieval loop and memfd_luo_discard_folios(), which could
   incorrectly process sparse file holes where pfn=0.</p>
<p>Fix by converting PFN to physical address with PFN_PHYS() and adding
the !pfolio-&gt;pfn check, matching the pattern used elsewhere in this file.</p>
<p>This issue was identified by the AI review.
https://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-46013"/>
  </entry>
</feed>
