<?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-29T20:04:58.828415+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-2022-49361</id>
    <title>CVE-2022-49361 — f2fs: fix to do sanity check for inline inode</title>
    <updated>2026-09-29T20:04:59.332693+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 to do sanity check for inline inode</p>
<p>Yanming reported a kernel bug in Bugzilla kernel [1], which can be
reproduced. The bug message is:</p>
<p>The kernel message is shown below:</p>
<p>kernel BUG at fs/inode.c:611!
Call Trace:
 evict+0x282/0x4e0
 __dentry_kill+0x2b2/0x4d0
 dput+0x2dd/0x720
 do_renameat2+0x596/0x970
 __x64_sys_rename+0x78/0x90
 do_syscall_64+0x3b/0x90</p>
<p>[1] https://bugzilla.kernel.org/show_bug.cgi?id=215895</p>
<p>The bug is due to fuzzed inode has both inline_data and encrypted flags.
During f2fs_evict_inode(), as the inode was deleted by rename(), it
will cause inline data conversion due to conflicting flags. The page
cache will be polluted and the panic will be triggered in clear_inode().</p>
<p>Try fixing the bug by doing more sanity checks for inline data inode in
sanity_check_inode().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-49361"/>
  </entry>
</feed>
