<?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://cve.radiocsirt.org</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 09:37:02 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15879</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15879</link>
      <description>bdu:2025-15879</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15879</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-56612</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-56612</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-56612</guid>
    </item>
    <item>
      <title>cnvd-2025-01681</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2025-01681</link>
      <description>cnvd-2025-01681</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2025-01681</guid>
    </item>
    <item>
      <title>EUVD-2026-313758</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313758</link>
      <description>EUVD-2026-313758</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313758</guid>
    </item>
    <item>
      <title>fkie_cve-2024-56612</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56612</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2024-56612</guid>
    </item>
    <item>
      <title>GHSA-vww8-w2qw-qhfg</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vww8-w2qw-qhfg</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-vww8-w2qw-qhfg</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56612</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56612</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 69 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/gup: handle NULL pages in unpin_user_pages() 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. Fix this by skipping NULL pages in unpin_user_pages(), just like unpin_folios() already does. Details: when booting on x86 with &amp;#34;numa=fake=2 movablecore=4G&amp;#34; on Linux 6.12, and running this:     tools/testing/selftests/mm/gup_longterm ...I get the following crash: 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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 69 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/gup: handle NULL pages in unpin_user_pages() 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. Fix this by skipping NULL pages in unpin_user_pages(), just like unpin_folios() already does. Details: when booting on x86 with &amp;#34;numa=fake=2 movablecore=4G&amp;#34; on Linux 6.12, and running this:     tools/testing/selftests/mm/gup_longterm ...I get the following crash: 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://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56612</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3762 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</guid>
    </item>
  </channel>
</rss>
