<?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://127.0.0.1:10001</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>Fri, 20 Nov 2026 23:30:58 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-31715</title>
      <link>https://127.0.0.1:10001/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://127.0.0.1:10001/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://127.0.0.1:10001/vuln/certfr-2026-avi-0605</link>
      <description>certfr-2026-avi-0605</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0605</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31715</title>
      <link>https://127.0.0.1:10001/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 218 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 218 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://127.0.0.1:10001/vuln/ubuntu-cve-2026-31715</guid>
    </item>
  </channel>
</rss>
