CVE-2022-49380

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

State
Published
Severity
Not scored
Published
Feb 26, 2025
Updated
Aug 15, 2026
Reserved
Feb 26, 2025

Read the record on cve.org

Description

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 to before f8b3c3fcf33105bc1ee7788e3b51b0a1ae42ae53Affected
  • 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 to before 2766ddaf45b69252bb8fe526b5b6e56904a9ae7aAffected
  • 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 to before bce859358d3d5940aa858e40ceee70ee6e76130eAffected
  • 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 to before 89d9a48d0cd30429463ea4e37ca83be6773ed5ebAffected
  • 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 to before ccffa99ae6a1f44797b57444c6a80382a42928feAffected
  • 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 to before 4d17e6fe9293d57081ffdc11e1cf313e25e8fd9eAffected
LinuxLinux
  • 3.8Affected
  • before 3.8Not affected
  • 5.4.198 through 5.4.*Not affected
  • 5.10.121 through 5.10.*Not affected
  • 5.15.46 through 5.15.*Not affected
  • 5.17.14 through 5.17.*Not affected
  • 5.18.3 through 5.18.*Not affected
  • 5.19 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.