<?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>Tue, 06 Oct 2026 07:55:51 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-03607</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-03607</link>
      <description>bdu:2025-03607</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-03607</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-26871</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-26871</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-26871</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0546 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0546</link>
      <description>certfr-2024-avi-0546</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0546</guid>
    </item>
    <item>
      <title>EUVD-2026-312637</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312637</link>
      <description>EUVD-2026-312637</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312637</guid>
    </item>
    <item>
      <title>fkie_cve-2024-26871</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-26871</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix NULL pointer dereference in f2fs_submit_page_write()&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000014
RIP: 0010:f2fs_submit_page_write+0x6cf/0x780 [f2fs]
Call Trace:
&amp;lt;TASK&amp;gt;
? show_regs+0x6e/0x80
? __die+0x29/0x70
? page_fault_oops+0x154/0x4a0
? prb_read_valid+0x20/0x30
? __irq_work_queue_local+0x39/0xd0
? irq_work_queue+0x36/0x70
? do_user_addr_fault+0x314/0x6c0
? exc_page_fault+0x7d/0x190
? asm_exc_page_fault+0x2b/0x30
? f2fs_submit_page_write+0x6cf/0x780 [f2fs]
? f2fs_submit_page_write+0x736/0x780 [f2fs]
do_write_page+0x50/0x170 [f2fs]
f2fs_outplace_write_data+0x61/0xb0 [f2fs]
f2fs_do_write_data_page+0x3f8/0x660 [f2fs]
f2fs_write_single_data_page+0x5bb/0x7a0 [f2fs]
f2fs_write_cache_pages+0x3da/0xbe0 [f2fs]
...
It is possible that other threads have added this fio to io-&amp;gt;bio
and submitted the io-&amp;gt;bio before entering f2fs_submit_page_write().
At this point io-&amp;gt;bio = NULL.
If is_end_zone_blkaddr(sbi, fio-&amp;gt;new_blkaddr) of this fio is true,
then an NULL pointer dereference error occurs at bio_get(io-&amp;gt;bio).
The original code for determining zone end was after &amp;#34;out:&amp;#34;,
which would have missed some fio who is zone end. I&amp;#39;ve moved
 this code before &amp;#34;skip:&amp;#34; to make sure it&amp;#39;s done for each fio.&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;f2fs: fix NULL pointer dereference in f2fs_submit_page_write()&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000014
RIP: 0010:f2fs_submit_page_write+0x6cf/0x780 [f2fs]
Call Trace:
&amp;lt;TASK&amp;gt;
? show_regs+0x6e/0x80
? __die+0x29/0x70
? page_fault_oops+0x154/0x4a0
? prb_read_valid+0x20/0x30
? __irq_work_queue_local+0x39/0xd0
? irq_work_queue+0x36/0x70
? do_user_addr_fault+0x314/0x6c0
? exc_page_fault+0x7d/0x190
? asm_exc_page_fault+0x2b/0x30
? f2fs_submit_page_write+0x6cf/0x780 [f2fs]
? f2fs_submit_page_write+0x736/0x780 [f2fs]
do_write_page+0x50/0x170 [f2fs]
f2fs_outplace_write_data+0x61/0xb0 [f2fs]
f2fs_do_write_data_page+0x3f8/0x660 [f2fs]
f2fs_write_single_data_page+0x5bb/0x7a0 [f2fs]
f2fs_write_cache_pages+0x3da/0xbe0 [f2fs]
...
It is possible that other threads have added this fio to io-&amp;gt;bio
and submitted the io-&amp;gt;bio before entering f2fs_submit_page_write().
At this point io-&amp;gt;bio = NULL.
If is_end_zone_blkaddr(sbi, fio-&amp;gt;new_blkaddr) of this fio is true,
then an NULL pointer dereference error occurs at bio_get(io-&amp;gt;bio).
The original code for determining zone end was after &amp;#34;out:&amp;#34;,
which would have missed some fio who is zone end. I&amp;#39;ve moved
 this code before &amp;#34;skip:&amp;#34; to make sure it&amp;#39;s done for each fio.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-26871</guid>
    </item>
    <item>
      <title>GHSA-63c9-q9c6-qgqh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-63c9-q9c6-qgqh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix NULL pointer dereference in f2fs_submit_page_write()&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000014
RIP: 0010:f2fs_submit_page_write+0x6cf/0x780 [f2fs]
Call Trace:
&amp;lt;TASK&amp;gt;
? show_regs+0x6e/0x80
? __die+0x29/0x70
? page_fault_oops+0x154/0x4a0
? prb_read_valid+0x20/0x30
? __irq_work_queue_local+0x39/0xd0
? irq_work_queue+0x36/0x70
? do_user_addr_fault+0x314/0x6c0
? exc_page_fault+0x7d/0x190
? asm_exc_page_fault+0x2b/0x30
? f2fs_submit_page_write+0x6cf/0x780 [f2fs]
? f2fs_submit_page_write+0x736/0x780 [f2fs]
do_write_page+0x50/0x170 [f2fs]
f2fs_outplace_write_data+0x61/0xb0 [f2fs]
f2fs_do_write_data_page+0x3f8/0x660 [f2fs]
f2fs_write_single_data_page+0x5bb/0x7a0 [f2fs]
f2fs_write_cache_pages+0x3da/0xbe0 [f2fs]
...
It is possible that other threads have added this fio to io-&amp;gt;bio
and submitted the io-&amp;gt;bio before entering f2fs_submit_page_write().
At this point io-&amp;gt;bio = NULL.
If is_end_zone_blkaddr(sbi, fio-&amp;gt;new_blkaddr) of this fio is true,
then an NULL pointer dereference error occurs at bio_get(io-&amp;gt;bio).
The original code for determining zone end was after &amp;#34;out:&amp;#34;,
which would have missed some fio who is zone end. I&amp;#39;ve moved
 this code before &amp;#34;skip:&amp;#34; to make sure it&amp;#39;s done for each fio.&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;f2fs: fix NULL pointer dereference in f2fs_submit_page_write()&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000014
RIP: 0010:f2fs_submit_page_write+0x6cf/0x780 [f2fs]
Call Trace:
&amp;lt;TASK&amp;gt;
? show_regs+0x6e/0x80
? __die+0x29/0x70
? page_fault_oops+0x154/0x4a0
? prb_read_valid+0x20/0x30
? __irq_work_queue_local+0x39/0xd0
? irq_work_queue+0x36/0x70
? do_user_addr_fault+0x314/0x6c0
? exc_page_fault+0x7d/0x190
? asm_exc_page_fault+0x2b/0x30
? f2fs_submit_page_write+0x6cf/0x780 [f2fs]
? f2fs_submit_page_write+0x736/0x780 [f2fs]
do_write_page+0x50/0x170 [f2fs]
f2fs_outplace_write_data+0x61/0xb0 [f2fs]
f2fs_do_write_data_page+0x3f8/0x660 [f2fs]
f2fs_write_single_data_page+0x5bb/0x7a0 [f2fs]
f2fs_write_cache_pages+0x3da/0xbe0 [f2fs]
...
It is possible that other threads have added this fio to io-&amp;gt;bio
and submitted the io-&amp;gt;bio before entering f2fs_submit_page_write().
At this point io-&amp;gt;bio = NULL.
If is_end_zone_blkaddr(sbi, fio-&amp;gt;new_blkaddr) of this fio is true,
then an NULL pointer dereference error occurs at bio_get(io-&amp;gt;bio).
The original code for determining zone end was after &amp;#34;out:&amp;#34;,
which would have missed some fio who is zone end. I&amp;#39;ve moved
 this code before &amp;#34;skip:&amp;#34; to make sure it&amp;#39;s done for each fio.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-63c9-q9c6-qgqh</guid>
    </item>
    <item>
      <title>gsd-2024-26871</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-26871</link>
      <description>gsd-2024-26871</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-26871</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26871</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26871</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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix NULL pointer dereference in f2fs_submit_page_write() BUG: kernel NULL pointer dereference, address: 0000000000000014 RIP: 0010:f2fs_submit_page_write+0x6cf/0x780 [f2fs] Call Trace: &amp;lt;TASK&amp;gt; ? show_regs+0x6e/0x80 ? __die+0x29/0x70 ? page_fault_oops+0x154/0x4a0 ? prb_read_valid+0x20/0x30 ? __irq_work_queue_local+0x39/0xd0 ? irq_work_queue+0x36/0x70 ? do_user_addr_fault+0x314/0x6c0 ? exc_page_fault+0x7d/0x190 ? asm_exc_page_fault+0x2b/0x30 ? f2fs_submit_page_write+0x6cf/0x780 [f2fs] ? f2fs_submit_page_write+0x736/0x780 [f2fs] do_write_page+0x50/0x170 [f2fs] f2fs_outplace_write_data+0x61/0xb0 [f2fs] f2fs_do_write_data_page+0x3f8/0x660 [f2fs] f2fs_write_single_data_page+0x5bb/0x7a0 [f2fs] f2fs_write_cache_pages+0x3da/0xbe0 [f2fs] ... It is possible that other threads have added this fio to io-&amp;gt;bio and submitted the io-&amp;gt;bio before entering f2fs_submit_page_write(). At this point io-&amp;gt;bio = NULL. If is_end_zone_blkaddr(sbi, fio-&amp;gt;new_blkaddr) of this fio is true, then an NULL pointer dereference error occurs at bio_get(io-&amp;gt;bio). The original code for determining zone end was after &amp;#34;out:&amp;#34;, which would have missed some fio who is zone end. I&amp;#39;ve moved  this code before &amp;#34;skip:&amp;#34; to make sure it&amp;#39;s done for each fio.&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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix NULL pointer dereference in f2fs_submit_page_write() BUG: kernel NULL pointer dereference, address: 0000000000000014 RIP: 0010:f2fs_submit_page_write+0x6cf/0x780 [f2fs] Call Trace: &amp;lt;TASK&amp;gt; ? show_regs+0x6e/0x80 ? __die+0x29/0x70 ? page_fault_oops+0x154/0x4a0 ? prb_read_valid+0x20/0x30 ? __irq_work_queue_local+0x39/0xd0 ? irq_work_queue+0x36/0x70 ? do_user_addr_fault+0x314/0x6c0 ? exc_page_fault+0x7d/0x190 ? asm_exc_page_fault+0x2b/0x30 ? f2fs_submit_page_write+0x6cf/0x780 [f2fs] ? f2fs_submit_page_write+0x736/0x780 [f2fs] do_write_page+0x50/0x170 [f2fs] f2fs_outplace_write_data+0x61/0xb0 [f2fs] f2fs_do_write_data_page+0x3f8/0x660 [f2fs] f2fs_write_single_data_page+0x5bb/0x7a0 [f2fs] f2fs_write_cache_pages+0x3da/0xbe0 [f2fs] ... It is possible that other threads have added this fio to io-&amp;gt;bio and submitted the io-&amp;gt;bio before entering f2fs_submit_page_write(). At this point io-&amp;gt;bio = NULL. If is_end_zone_blkaddr(sbi, fio-&amp;gt;new_blkaddr) of this fio is true, then an NULL pointer dereference error occurs at bio_get(io-&amp;gt;bio). The original code for determining zone end was after &amp;#34;out:&amp;#34;, which would have missed some fio who is zone end. I&amp;#39;ve moved  this code before &amp;#34;skip:&amp;#34; to make sure it&amp;#39;s done for each fio.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26871</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0920 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0920</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0920</guid>
    </item>
  </channel>
</rss>
