<?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>Wed, 30 Sep 2026 07:58:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80685 — mm/util: don't read __page_2 for order-1 folios in snapshot_page()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80685</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/util: don&amp;#39;t read __page_2 for order-1 folios in snapshot_page()&lt;/p&gt;
&lt;p&gt;snapshot_page() currently reads __page_2 after checking nr_pages &amp;gt; 1, but
it should only do so when nr_pages &amp;gt; 2.&lt;/p&gt;
&lt;p&gt;If an order-1 folio is allocated at the end of a vmemmap section,
__page_2 will not exist and reading it will cause a fault.&lt;/p&gt;
&lt;p&gt;During DLPAR memory remove on a 22 TB ppc64le LPAR, snapshot_page() oopsed
on the page isolation path while reading an order-1 folio&amp;#39;s __page_2 from
an adjacent absent section (unmapped vmemmap).&lt;/p&gt;
&lt;p&gt;Fix this to avoid reading memmap that doesn&amp;#39;t exist (e.g., a vmemmap
hole).&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/util: don&amp;#39;t read __page_2 for order-1 folios in snapshot_page()&lt;/p&gt;
&lt;p&gt;snapshot_page() currently reads __page_2 after checking nr_pages &amp;gt; 1, but
it should only do so when nr_pages &amp;gt; 2.&lt;/p&gt;
&lt;p&gt;If an order-1 folio is allocated at the end of a vmemmap section,
__page_2 will not exist and reading it will cause a fault.&lt;/p&gt;
&lt;p&gt;During DLPAR memory remove on a 22 TB ppc64le LPAR, snapshot_page() oopsed
on the page isolation path while reading an order-1 folio&amp;#39;s __page_2 from
an adjacent absent section (unmapped vmemmap).&lt;/p&gt;
&lt;p&gt;Fix this to avoid reading memmap that doesn&amp;#39;t exist (e.g., a vmemmap
hole).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80685</guid>
    </item>
  </channel>
</rss>
