<?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>Sun, 04 Oct 2026 00:37:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46013 — mm/memfd_luo: fix physical address conversion in put_folios cleanup</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46013</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/memfd_luo: fix physical address conversion in put_folios cleanup&lt;/p&gt;
&lt;p&gt;In memfd_luo_retrieve_folios()&amp;#39;s put_folios cleanup path:&lt;/p&gt;
&lt;p&gt;1. kho_restore_folio() expects a phys_addr_t (physical address) but
   receives a raw PFN (pfolio-&amp;gt;pfn). This causes kho_restore_page() to
   check the wrong physical address (pfn &amp;lt;&amp;lt; PAGE_SHIFT instead of the
   actual physical address).&lt;/p&gt;
&lt;p&gt;2. This loop lacks the !pfolio-&amp;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.&lt;/p&gt;
&lt;p&gt;Fix by converting PFN to physical address with PFN_PHYS() and adding
the !pfolio-&amp;gt;pfn check, matching the pattern used elsewhere in this file.&lt;/p&gt;
&lt;p&gt;This issue was identified by the AI review.
https://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn&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/memfd_luo: fix physical address conversion in put_folios cleanup&lt;/p&gt;
&lt;p&gt;In memfd_luo_retrieve_folios()&amp;#39;s put_folios cleanup path:&lt;/p&gt;
&lt;p&gt;1. kho_restore_folio() expects a phys_addr_t (physical address) but
   receives a raw PFN (pfolio-&amp;gt;pfn). This causes kho_restore_page() to
   check the wrong physical address (pfn &amp;lt;&amp;lt; PAGE_SHIFT instead of the
   actual physical address).&lt;/p&gt;
&lt;p&gt;2. This loop lacks the !pfolio-&amp;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.&lt;/p&gt;
&lt;p&gt;Fix by converting PFN to physical address with PFN_PHYS() and adding
the !pfolio-&amp;gt;pfn check, matching the pattern used elsewhere in this file.&lt;/p&gt;
&lt;p&gt;This issue was identified by the AI review.
https://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-46013</guid>
    </item>
  </channel>
</rss>
