<?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>Sat, 03 Oct 2026 23:25:01 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-31715</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-31715</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-31715</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0605 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0605</link>
      <description>certfr-2026-avi-0605</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0605</guid>
    </item>
    <item>
      <title>EUVD-2026-328676</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-328676</link>
      <description>EUVD-2026-328676</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-328676</guid>
    </item>
    <item>
      <title>fkie_cve-2026-31715</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-31715</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix UAF caused by decrementing sbi-&amp;gt;nr_pages[] in f2fs_write_end_io()&lt;/p&gt;
&lt;p&gt;The xfstests case &amp;#34;generic/107&amp;#34; and syzbot have both reported a NULL
pointer dereference.&lt;/p&gt;
&lt;p&gt;The concurrent scenario that triggers the panic is as follows:&lt;/p&gt;
&lt;p&gt;F2FS_WB_CP_DATA write callback          umount
                                        - f2fs_write_checkpoint
                                         - f2fs_wait_on_all_pages(sbi, F2FS_WB_CP_DATA)
- blk_mq_end_request
 - bio_endio
  - f2fs_write_end_io
   : dec_page_count(sbi, F2FS_WB_CP_DATA)
   : wake_up(&amp;amp;sbi-&amp;gt;cp_wait)
                                        - kill_f2fs_super
                                         - kill_block_super
                                          - f2fs_put_super
                                           : iput(sbi-&amp;gt;node_inode)
                                           : sbi-&amp;gt;node_inode = NULL
   : f2fs_in_warm_node_list
    - is_node_folio // sbi-&amp;gt;node_inode is NULL and panic&lt;/p&gt;
&lt;p&gt;The root cause is that f2fs_put_super() calls iput(sbi-&amp;gt;node_inode) and
sets sbi-&amp;gt;node_inode to NULL after sbi-&amp;gt;nr_pages[F2FS_WB_CP_DATA] is
decremented to zero. As a result, f2fs_in_warm_node_list() may
dereference a NULL node_inode when checking whether a folio belongs to
the node inode, leading to a panic.&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by calling f2fs_in_warm_node_list() before
decrementing sbi-&amp;gt;nr_pages[F2FS_WB_CP_DATA], thus preventing the
use-after-free condition.&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 UAF caused by decrementing sbi-&amp;gt;nr_pages[] in f2fs_write_end_io()&lt;/p&gt;
&lt;p&gt;The xfstests case &amp;#34;generic/107&amp;#34; and syzbot have both reported a NULL
pointer dereference.&lt;/p&gt;
&lt;p&gt;The concurrent scenario that triggers the panic is as follows:&lt;/p&gt;
&lt;p&gt;F2FS_WB_CP_DATA write callback          umount
                                        - f2fs_write_checkpoint
                                         - f2fs_wait_on_all_pages(sbi, F2FS_WB_CP_DATA)
- blk_mq_end_request
 - bio_endio
  - f2fs_write_end_io
   : dec_page_count(sbi, F2FS_WB_CP_DATA)
   : wake_up(&amp;amp;sbi-&amp;gt;cp_wait)
                                        - kill_f2fs_super
                                         - kill_block_super
                                          - f2fs_put_super
                                           : iput(sbi-&amp;gt;node_inode)
                                           : sbi-&amp;gt;node_inode = NULL
   : f2fs_in_warm_node_list
    - is_node_folio // sbi-&amp;gt;node_inode is NULL and panic&lt;/p&gt;
&lt;p&gt;The root cause is that f2fs_put_super() calls iput(sbi-&amp;gt;node_inode) and
sets sbi-&amp;gt;node_inode to NULL after sbi-&amp;gt;nr_pages[F2FS_WB_CP_DATA] is
decremented to zero. As a result, f2fs_in_warm_node_list() may
dereference a NULL node_inode when checking whether a folio belongs to
the node inode, leading to a panic.&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by calling f2fs_in_warm_node_list() before
decrementing sbi-&amp;gt;nr_pages[F2FS_WB_CP_DATA], thus preventing the
use-after-free condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-31715</guid>
    </item>
    <item>
      <title>GHSA-5pg7-fr46-jx8j</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5pg7-fr46-jx8j</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix UAF caused by decrementing sbi-&amp;gt;nr_pages[] in f2fs_write_end_io()&lt;/p&gt;
&lt;p&gt;The xfstests case &amp;#34;generic/107&amp;#34; and syzbot have both reported a NULL
pointer dereference.&lt;/p&gt;
&lt;p&gt;The concurrent scenario that triggers the panic is as follows:&lt;/p&gt;
&lt;p&gt;F2FS_WB_CP_DATA write callback          umount
                                        - f2fs_write_checkpoint
                                         - f2fs_wait_on_all_pages(sbi, F2FS_WB_CP_DATA)
- blk_mq_end_request
 - bio_endio
  - f2fs_write_end_io
   : dec_page_count(sbi, F2FS_WB_CP_DATA)
   : wake_up(&amp;amp;sbi-&amp;gt;cp_wait)
                                        - kill_f2fs_super
                                         - kill_block_super
                                          - f2fs_put_super
                                           : iput(sbi-&amp;gt;node_inode)
                                           : sbi-&amp;gt;node_inode = NULL
   : f2fs_in_warm_node_list
    - is_node_folio // sbi-&amp;gt;node_inode is NULL and panic&lt;/p&gt;
&lt;p&gt;The root cause is that f2fs_put_super() calls iput(sbi-&amp;gt;node_inode) and
sets sbi-&amp;gt;node_inode to NULL after sbi-&amp;gt;nr_pages[F2FS_WB_CP_DATA] is
decremented to zero. As a result, f2fs_in_warm_node_list() may
dereference a NULL node_inode when checking whether a folio belongs to
the node inode, leading to a panic.&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by calling f2fs_in_warm_node_list() before
decrementing sbi-&amp;gt;nr_pages[F2FS_WB_CP_DATA], thus preventing the
use-after-free condition.&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 UAF caused by decrementing sbi-&amp;gt;nr_pages[] in f2fs_write_end_io()&lt;/p&gt;
&lt;p&gt;The xfstests case &amp;#34;generic/107&amp;#34; and syzbot have both reported a NULL
pointer dereference.&lt;/p&gt;
&lt;p&gt;The concurrent scenario that triggers the panic is as follows:&lt;/p&gt;
&lt;p&gt;F2FS_WB_CP_DATA write callback          umount
                                        - f2fs_write_checkpoint
                                         - f2fs_wait_on_all_pages(sbi, F2FS_WB_CP_DATA)
- blk_mq_end_request
 - bio_endio
  - f2fs_write_end_io
   : dec_page_count(sbi, F2FS_WB_CP_DATA)
   : wake_up(&amp;amp;sbi-&amp;gt;cp_wait)
                                        - kill_f2fs_super
                                         - kill_block_super
                                          - f2fs_put_super
                                           : iput(sbi-&amp;gt;node_inode)
                                           : sbi-&amp;gt;node_inode = NULL
   : f2fs_in_warm_node_list
    - is_node_folio // sbi-&amp;gt;node_inode is NULL and panic&lt;/p&gt;
&lt;p&gt;The root cause is that f2fs_put_super() calls iput(sbi-&amp;gt;node_inode) and
sets sbi-&amp;gt;node_inode to NULL after sbi-&amp;gt;nr_pages[F2FS_WB_CP_DATA] is
decremented to zero. As a result, f2fs_in_warm_node_list() may
dereference a NULL node_inode when checking whether a folio belongs to
the node inode, leading to a panic.&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by calling f2fs_in_warm_node_list() before
decrementing sbi-&amp;gt;nr_pages[F2FS_WB_CP_DATA], thus preventing the
use-after-free condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5pg7-fr46-jx8j</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-31715 — f2fs: fix UAF caused by decrementing sbi-&gt;nr_pages[] in f2fs_write_end_io()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-31715</link>
      <description>msrc_CVE-2026-31715</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-31715</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10793-1 — kernel-devel-7.0.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10793-1</link>
      <description>&lt;p&gt;kernel-devel-7.0.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.0.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10793-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31715</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31715</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 217 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix UAF caused by decrementing sbi-&amp;gt;nr_pages[] in f2fs_write_end_io() The xfstests case &amp;#34;generic/107&amp;#34; and syzbot have both reported a NULL pointer dereference. The concurrent scenario that triggers the panic is as follows: F2FS_WB_CP_DATA write callback          umount                                         - f2fs_write_checkpoint                                          - f2fs_wait_on_all_pages(sbi, F2FS_WB_CP_DATA) - blk_mq_end_request  - bio_endio   - f2fs_write_end_io    : dec_page_count(sbi, F2FS_WB_CP_DATA)    : wake_up(&amp;amp;sbi-&amp;gt;cp_wait)                                         - kill_f2fs_super                                          - kill_block_super                                           - f2fs_put_super                                            : iput(sbi-&amp;gt;node_inode)                                            : sbi-&amp;gt;node_inode = NULL    : f2fs_in_warm_node_list     - is_node_folio // sbi-&amp;gt;node_inode is NULL and panic The root cause is that f2fs_put_super() calls iput(sbi-&amp;gt;node_inode) and sets sbi-&amp;gt;node_inode to NULL after sbi-&amp;gt;nr_pages[F2FS_WB_CP_DATA] is decremented to zero. As a result, f2fs_in_warm_node_list() may dereference a NULL node_inode when checking whether a folio belongs to the node inode, leading to a panic. This patch fixes the issue by calling f2fs_in_warm_node_list() before decrementing sbi-&amp;gt;nr_pages[F2FS_WB_CP_DATA], thus preventing the use-after-free condition.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 217 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix UAF caused by decrementing sbi-&amp;gt;nr_pages[] in f2fs_write_end_io() The xfstests case &amp;#34;generic/107&amp;#34; and syzbot have both reported a NULL pointer dereference. The concurrent scenario that triggers the panic is as follows: F2FS_WB_CP_DATA write callback          umount                                         - f2fs_write_checkpoint                                          - f2fs_wait_on_all_pages(sbi, F2FS_WB_CP_DATA) - blk_mq_end_request  - bio_endio   - f2fs_write_end_io    : dec_page_count(sbi, F2FS_WB_CP_DATA)    : wake_up(&amp;amp;sbi-&amp;gt;cp_wait)                                         - kill_f2fs_super                                          - kill_block_super                                           - f2fs_put_super                                            : iput(sbi-&amp;gt;node_inode)                                            : sbi-&amp;gt;node_inode = NULL    : f2fs_in_warm_node_list     - is_node_folio // sbi-&amp;gt;node_inode is NULL and panic The root cause is that f2fs_put_super() calls iput(sbi-&amp;gt;node_inode) and sets sbi-&amp;gt;node_inode to NULL after sbi-&amp;gt;nr_pages[F2FS_WB_CP_DATA] is decremented to zero. As a result, f2fs_in_warm_node_list() may dereference a NULL node_inode when checking whether a folio belongs to the node inode, leading to a panic. This patch fixes the issue by calling f2fs_in_warm_node_list() before decrementing sbi-&amp;gt;nr_pages[F2FS_WB_CP_DATA], thus preventing the use-after-free condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31715</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1346 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1346</link>
      <description>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Root-Rechte zu erlangen, um Sicherheitsmechanismen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder Auswirkungen unbestimmter Art zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Root-Rechte zu erlangen, um Sicherheitsmechanismen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder Auswirkungen unbestimmter Art zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1346</guid>
    </item>
  </channel>
</rss>
