<?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-03T23:10:29.886742+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-2024-57881</id>
    <title>CVE-2024-57881 — mm/page_alloc: don't call pfn_to_page() on possibly non-existent PFN in split_large_buddy()</title>
    <updated>2026-10-03T23:10:31.139080+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/page_alloc: don't call pfn_to_page() on possibly non-existent PFN in split_large_buddy()</p>
<p>In split_large_buddy(), we might call pfn_to_page() on a PFN that might
not exist.  In corner cases, such as when freeing the highest pageblock in
the last memory section, this could result with CONFIG_SPARSEMEM &amp;&amp;
!CONFIG_SPARSEMEM_EXTREME in __pfn_to_section() returning NULL and and
__section_mem_map_addr() dereferencing that NULL pointer.</p>
<p>Let's fix it, and avoid doing a pfn_to_page() call for the first
iteration, where we already have the page.</p>
<p>So far this was found by code inspection, but let's just CC stable as the
fix is easy.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-57881"/>
  </entry>
</feed>
