<?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>Tue, 29 Sep 2026 00:46:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-56612 — mm/gup: handle NULL pages in unpin_user_pages()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-56612</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/gup: handle NULL pages in unpin_user_pages()&lt;/p&gt;
&lt;p&gt;The recent addition of &amp;#34;pofs&amp;#34; (pages or folios) handling to gup has a
flaw: it assumes that unpin_user_pages() handles NULL pages in the pages**
array.  That&amp;#39;s not the case, as I discovered when I ran on a new
configuration on my test machine.&lt;/p&gt;
&lt;p&gt;Fix this by skipping NULL pages in unpin_user_pages(), just like
unpin_folios() already does.&lt;/p&gt;
&lt;p&gt;Details: when booting on x86 with &amp;#34;numa=fake=2 movablecore=4G&amp;#34; on Linux
6.12, and running this:&lt;/p&gt;
&lt;p&gt;tools/testing/selftests/mm/gup_longterm&lt;/p&gt;
&lt;p&gt;...I get the following crash:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000008
RIP: 0010:sanity_check_pinned_pages+0x3a/0x2d0
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 ? __die_body+0x66/0xb0
 ? page_fault_oops+0x30c/0x3b0
 ? do_user_addr_fault+0x6c3/0x720
 ? irqentry_enter+0x34/0x60
 ? exc_page_fault+0x68/0x100
 ? asm_exc_page_fault+0x22/0x30
 ? sanity_check_pinned_pages+0x3a/0x2d0
 unpin_user_pages+0x24/0xe0
 check_and_migrate_movable_pages_or_folios+0x455/0x4b0
 __gup_longterm_locked+0x3bf/0x820
 ? mmap_read_lock_killable+0x12/0x50
 ? __pfx_mmap_read_lock_killable+0x10/0x10
 pin_user_pages+0x66/0xa0
 gup_test_ioctl+0x358/0xb20
 __se_sys_ioctl+0x6b/0xc0
 do_syscall_64+0x7b/0x150
 entry_SYSCALL_64_after_hwframe+0x76/0x7e&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/gup: handle NULL pages in unpin_user_pages()&lt;/p&gt;
&lt;p&gt;The recent addition of &amp;#34;pofs&amp;#34; (pages or folios) handling to gup has a
flaw: it assumes that unpin_user_pages() handles NULL pages in the pages**
array.  That&amp;#39;s not the case, as I discovered when I ran on a new
configuration on my test machine.&lt;/p&gt;
&lt;p&gt;Fix this by skipping NULL pages in unpin_user_pages(), just like
unpin_folios() already does.&lt;/p&gt;
&lt;p&gt;Details: when booting on x86 with &amp;#34;numa=fake=2 movablecore=4G&amp;#34; on Linux
6.12, and running this:&lt;/p&gt;
&lt;p&gt;tools/testing/selftests/mm/gup_longterm&lt;/p&gt;
&lt;p&gt;...I get the following crash:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000008
RIP: 0010:sanity_check_pinned_pages+0x3a/0x2d0
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 ? __die_body+0x66/0xb0
 ? page_fault_oops+0x30c/0x3b0
 ? do_user_addr_fault+0x6c3/0x720
 ? irqentry_enter+0x34/0x60
 ? exc_page_fault+0x68/0x100
 ? asm_exc_page_fault+0x22/0x30
 ? sanity_check_pinned_pages+0x3a/0x2d0
 unpin_user_pages+0x24/0xe0
 check_and_migrate_movable_pages_or_folios+0x455/0x4b0
 __gup_longterm_locked+0x3bf/0x820
 ? mmap_read_lock_killable+0x12/0x50
 ? __pfx_mmap_read_lock_killable+0x10/0x10
 pin_user_pages+0x66/0xa0
 gup_test_ioctl+0x358/0xb20
 __se_sys_ioctl+0x6b/0xc0
 do_syscall_64+0x7b/0x150
 entry_SYSCALL_64_after_hwframe+0x76/0x7e&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-56612</guid>
    </item>
  </channel>
</rss>
