Bug 2347962 (CVE-2022-49380) - CVE-2022-49380 kernel: f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count()
Summary: CVE-2022-49380 kernel: f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_cou...
Keywords:
Status: NEW
Alias: CVE-2022-49380
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-26 03:12 UTC by OSIDB Bzimport
Modified: 2025-02-26 17:15 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-02-26 03:12:48 UTC
In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count()

As Yanming reported in bugzilla:

https://bugzilla.kernel.org/show_bug.cgi?id=215897

I have encountered a bug in F2FS file system in kernel v5.17.

The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can
reproduce the bug by running the following commands:

The kernel message is shown below:

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

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.

Comment 1 Avinash Hanwate 2025-02-26 12:49:40 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022647-CVE-2022-49380-24ee@gregkh/T

Comment 2 Avinash Hanwate 2025-02-26 17:15:07 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022647-CVE-2022-49380-24ee@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.