<?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>Mon, 19 Oct 2026 05:59:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49380 — f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49380</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count()&lt;/p&gt;
&lt;p&gt;As Yanming reported in bugzilla:&lt;/p&gt;
&lt;p&gt;https://bugzilla.kernel.org/show_bug.cgi?id=215897&lt;/p&gt;
&lt;p&gt;I have encountered a bug in F2FS file system in kernel v5.17.&lt;/p&gt;
&lt;p&gt;The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can
reproduce the bug by running the following commands:&lt;/p&gt;
&lt;p&gt;The kernel message is shown below:&lt;/p&gt;
&lt;p&gt;kernel BUG at fs/f2fs/f2fs.h:2511!
Call Trace:
 f2fs_remove_inode_page+0x2a2/0x830
 f2fs_evict_inode+0x9b7/0x1510
 evict+0x282/0x4e0
 do_unlinkat+0x33a/0x540
 __x64_sys_unlinkat+0x8e/0xd0
 do_syscall_64+0x3b/0x90
 entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;The root cause is: .total_valid_block_count or .total_valid_node_count
could fuzzed to zero, then once dec_valid_node_count() was called, it
will cause BUG_ON(), this patch fixes to print warning info and set
SBI_NEED_FSCK into CP instead of panic.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count()&lt;/p&gt;
&lt;p&gt;As Yanming reported in bugzilla:&lt;/p&gt;
&lt;p&gt;https://bugzilla.kernel.org/show_bug.cgi?id=215897&lt;/p&gt;
&lt;p&gt;I have encountered a bug in F2FS file system in kernel v5.17.&lt;/p&gt;
&lt;p&gt;The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can
reproduce the bug by running the following commands:&lt;/p&gt;
&lt;p&gt;The kernel message is shown below:&lt;/p&gt;
&lt;p&gt;kernel BUG at fs/f2fs/f2fs.h:2511!
Call Trace:
 f2fs_remove_inode_page+0x2a2/0x830
 f2fs_evict_inode+0x9b7/0x1510
 evict+0x282/0x4e0
 do_unlinkat+0x33a/0x540
 __x64_sys_unlinkat+0x8e/0xd0
 do_syscall_64+0x3b/0x90
 entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;The root cause is: .total_valid_block_count or .total_valid_node_count
could fuzzed to zero, then once dec_valid_node_count() was called, it
will cause BUG_ON(), this patch fixes to print warning info and set
SBI_NEED_FSCK into CP instead of panic.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49380</guid>
    </item>
  </channel>
</rss>
