<?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>Wed, 07 Oct 2026 10:43:49 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04165</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04165</link>
      <description>bdu:2026-04165</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04165</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-23265</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-23265</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-23265</guid>
    </item>
    <item>
      <title>EUVD-2026-315438</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315438</link>
      <description>EUVD-2026-315438</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315438</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23265</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23265</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to do sanity check on node footer in {read,write}_end_io&lt;/p&gt;
&lt;p&gt;-----------[ cut here ]------------
kernel BUG at fs/f2fs/data.c:358!
Call Trace:
 &amp;lt;IRQ&amp;gt;
 blk_update_request+0x5eb/0xe70 block/blk-mq.c:987
 blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1149
 blk_complete_reqs block/blk-mq.c:1224 [inline]
 blk_done_softirq+0x107/0x160 block/blk-mq.c:1229
 handle_softirqs+0x283/0x870 kernel/softirq.c:579
 __do_softirq kernel/softirq.c:613 [inline]
 invoke_softirq kernel/softirq.c:453 [inline]
 __irq_exit_rcu+0xca/0x1f0 kernel/softirq.c:680
 irq_exit_rcu+0x9/0x30 kernel/softirq.c:696
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1050 [inline]
 sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1050
 &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;In f2fs_write_end_io(), it detects there is inconsistency in between
node page index (nid) and footer.nid of node page.&lt;/p&gt;
&lt;p&gt;If footer of node page is corrupted in fuzzed image, then we load corrupted
node page w/ async method, e.g. f2fs_ra_node_pages() or f2fs_ra_node_page(),
in where we won&amp;#39;t do sanity check on node footer, once node page becomes
dirty, we will encounter this bug after node page writeback.&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 to do sanity check on node footer in {read,write}_end_io&lt;/p&gt;
&lt;p&gt;-----------[ cut here ]------------
kernel BUG at fs/f2fs/data.c:358!
Call Trace:
 &amp;lt;IRQ&amp;gt;
 blk_update_request+0x5eb/0xe70 block/blk-mq.c:987
 blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1149
 blk_complete_reqs block/blk-mq.c:1224 [inline]
 blk_done_softirq+0x107/0x160 block/blk-mq.c:1229
 handle_softirqs+0x283/0x870 kernel/softirq.c:579
 __do_softirq kernel/softirq.c:613 [inline]
 invoke_softirq kernel/softirq.c:453 [inline]
 __irq_exit_rcu+0xca/0x1f0 kernel/softirq.c:680
 irq_exit_rcu+0x9/0x30 kernel/softirq.c:696
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1050 [inline]
 sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1050
 &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;In f2fs_write_end_io(), it detects there is inconsistency in between
node page index (nid) and footer.nid of node page.&lt;/p&gt;
&lt;p&gt;If footer of node page is corrupted in fuzzed image, then we load corrupted
node page w/ async method, e.g. f2fs_ra_node_pages() or f2fs_ra_node_page(),
in where we won&amp;#39;t do sanity check on node footer, once node page becomes
dirty, we will encounter this bug after node page writeback.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23265</guid>
    </item>
    <item>
      <title>GHSA-h5gx-jh73-27w4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h5gx-jh73-27w4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to do sanity check on node footer in {read,write}_end_io&lt;/p&gt;
&lt;p&gt;-----------[ cut here ]------------
kernel BUG at fs/f2fs/data.c:358!
Call Trace:
 &amp;lt;IRQ&amp;gt;
 blk_update_request+0x5eb/0xe70 block/blk-mq.c:987
 blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1149
 blk_complete_reqs block/blk-mq.c:1224 [inline]
 blk_done_softirq+0x107/0x160 block/blk-mq.c:1229
 handle_softirqs+0x283/0x870 kernel/softirq.c:579
 __do_softirq kernel/softirq.c:613 [inline]
 invoke_softirq kernel/softirq.c:453 [inline]
 __irq_exit_rcu+0xca/0x1f0 kernel/softirq.c:680
 irq_exit_rcu+0x9/0x30 kernel/softirq.c:696
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1050 [inline]
 sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1050
 &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;In f2fs_write_end_io(), it detects there is inconsistency in between
node page index (nid) and footer.nid of node page.&lt;/p&gt;
&lt;p&gt;If footer of node page is corrupted in fuzzed image, then we load corrupted
node page w/ async method, e.g. f2fs_ra_node_pages() or f2fs_ra_node_page(),
in where we won&amp;#39;t do sanity check on node footer, once node page becomes
dirty, we will encounter this bug after node page writeback.&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 to do sanity check on node footer in {read,write}_end_io&lt;/p&gt;
&lt;p&gt;-----------[ cut here ]------------
kernel BUG at fs/f2fs/data.c:358!
Call Trace:
 &amp;lt;IRQ&amp;gt;
 blk_update_request+0x5eb/0xe70 block/blk-mq.c:987
 blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1149
 blk_complete_reqs block/blk-mq.c:1224 [inline]
 blk_done_softirq+0x107/0x160 block/blk-mq.c:1229
 handle_softirqs+0x283/0x870 kernel/softirq.c:579
 __do_softirq kernel/softirq.c:613 [inline]
 invoke_softirq kernel/softirq.c:453 [inline]
 __irq_exit_rcu+0xca/0x1f0 kernel/softirq.c:680
 irq_exit_rcu+0x9/0x30 kernel/softirq.c:696
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1050 [inline]
 sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1050
 &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;In f2fs_write_end_io(), it detects there is inconsistency in between
node page index (nid) and footer.nid of node page.&lt;/p&gt;
&lt;p&gt;If footer of node page is corrupted in fuzzed image, then we load corrupted
node page w/ async method, e.g. f2fs_ra_node_pages() or f2fs_ra_node_page(),
in where we won&amp;#39;t do sanity check on node footer, once node page becomes
dirty, we will encounter this bug after node page writeback.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h5gx-jh73-27w4</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-23265 — f2fs: fix to do sanity check on node footer in {read,write}_end_io</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-23265</link>
      <description>msrc_CVE-2026-23265</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-23265</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23265</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23265</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 234 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on node footer in {read,write}_end_io -----------[ cut here ]------------ kernel BUG at fs/f2fs/data.c:358! Call Trace:  &amp;lt;IRQ&amp;gt;  blk_update_request+0x5eb/0xe70 block/blk-mq.c:987  blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1149  blk_complete_reqs block/blk-mq.c:1224 [inline]  blk_done_softirq+0x107/0x160 block/blk-mq.c:1229  handle_softirqs+0x283/0x870 kernel/softirq.c:579  __do_softirq kernel/softirq.c:613 [inline]  invoke_softirq kernel/softirq.c:453 [inline]  __irq_exit_rcu+0xca/0x1f0 kernel/softirq.c:680  irq_exit_rcu+0x9/0x30 kernel/softirq.c:696  instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1050 [inline]  sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1050  &amp;lt;/IRQ&amp;gt; In f2fs_write_end_io(), it detects there is inconsistency in between node page index (nid) and footer.nid of node page. If footer of node page is corrupted in fuzzed image, then we load corrupted node page w/ async method, e.g. f2fs_ra_node_pages() or f2fs_ra_node_page(), in where we won&amp;#39;t do sanity check on node footer, once node page becomes dirty, we will encounter this bug after node page writeback.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 234 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on node footer in {read,write}_end_io -----------[ cut here ]------------ kernel BUG at fs/f2fs/data.c:358! Call Trace:  &amp;lt;IRQ&amp;gt;  blk_update_request+0x5eb/0xe70 block/blk-mq.c:987  blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1149  blk_complete_reqs block/blk-mq.c:1224 [inline]  blk_done_softirq+0x107/0x160 block/blk-mq.c:1229  handle_softirqs+0x283/0x870 kernel/softirq.c:579  __do_softirq kernel/softirq.c:613 [inline]  invoke_softirq kernel/softirq.c:453 [inline]  __irq_exit_rcu+0xca/0x1f0 kernel/softirq.c:680  irq_exit_rcu+0x9/0x30 kernel/softirq.c:696  instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1050 [inline]  sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1050  &amp;lt;/IRQ&amp;gt; In f2fs_write_end_io(), it detects there is inconsistency in between node page index (nid) and footer.nid of node page. If footer of node page is corrupted in fuzzed image, then we load corrupted node page w/ async method, e.g. f2fs_ra_node_pages() or f2fs_ra_node_page(), in where we won&amp;#39;t do sanity check on node footer, once node page becomes dirty, we will encounter this bug after node page writeback.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23265</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0790 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0790</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einem Denial-of-Service-Zustand, einer Rechteausweitung oder einer Speicherbeschädigung führen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einem Denial-of-Service-Zustand, einer Rechteausweitung oder einer Speicherbeschädigung führen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0790</guid>
    </item>
  </channel>
</rss>
