<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T17:17:40.612121+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-31715</id>
    <title>CVE-2026-31715 — f2fs: fix UAF caused by decrementing sbi-&gt;nr_pages[] in f2fs_write_end_io()</title>
    <updated>2026-09-29T17:17:40.614601+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>f2fs: fix UAF caused by decrementing sbi-&gt;nr_pages[] in f2fs_write_end_io()</p>
<p>The xfstests case "generic/107" and syzbot have both reported a NULL
pointer dereference.</p>
<p>The concurrent scenario that triggers the panic is as follows:</p>
<p>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;sbi-&gt;cp_wait)
                                        - kill_f2fs_super
                                         - kill_block_super
                                          - f2fs_put_super
                                           : iput(sbi-&gt;node_inode)
                                           : sbi-&gt;node_inode = NULL
   : f2fs_in_warm_node_list
    - is_node_folio // sbi-&gt;node_inode is NULL and panic</p>
<p>The root cause is that f2fs_put_super() calls iput(sbi-&gt;node_inode) and
sets sbi-&gt;node_inode to NULL after sbi-&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.</p>
<p>This patch fixes the issue by calling f2fs_in_warm_node_list() before
decrementing sbi-&gt;nr_pages[F2FS_WB_CP_DATA], thus preventing the
use-after-free condition.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-31715"/>
  </entry>
</feed>
