CVE-2022-49364

f2fs: fix to clear dirty inode in f2fs_evict_inode()

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 clear dirty inode in f2fs_evict_inode()

As Yanming reported in bugzilla:

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

The kernel message is shown below:

kernel BUG at fs/f2fs/inode.c:825! Call Trace: evict+0x282/0x4e0 __dentry_kill+0x2b2/0x4d0 shrink_dentry_list+0x17c/0x4f0 shrink_dcache_parent+0x143/0x1e0 do_one_tree+0x9/0x30 shrink_dcache_for_umount+0x51/0x120 generic_shutdown_super+0x5c/0x3a0 kill_block_super+0x90/0xd0 kill_f2fs_super+0x225/0x310 deactivate_locked_super+0x78/0xc0 cleanup_mnt+0x2b7/0x480 task_work_run+0xc8/0x150 exit_to_user_mode_prepare+0x14a/0x150 syscall_exit_to_user_mode+0x1d/0x40 do_syscall_64+0x48/0x90

The root cause is: inode node and dnode node share the same nid, so during f2fs_evict_inode(), dnode node truncation will invalidate its NAT entry, so when truncating inode node, it fails due to invalid NAT entry, result in inode is still marked as dirty, fix this issue by clearing dirty for inode and setting SBI_NEED_FSCK flag in filesystem.

output from dump.f2fs: [print_node_info: 354] Node ID [0xf:15] is inode i_nid[0] [0x f : 15]

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • a11b9f65eae766b17ec3451a6a1766f0a9d1dbff to before 54c116615c99e22aa08aa950757ed726e2f60821Affected
  • a11b9f65eae766b17ec3451a6a1766f0a9d1dbff to before ccd58045beb997544b94558a9156be4742628491Affected
  • a11b9f65eae766b17ec3451a6a1766f0a9d1dbff to before c9196d21359be8c7ee231029d13682273925fd00Affected
  • a11b9f65eae766b17ec3451a6a1766f0a9d1dbff to before 03c9373b15fa1c245ec99b2b5e7ba209eae4ef42Affected
  • a11b9f65eae766b17ec3451a6a1766f0a9d1dbff to before c469953917b319d415fd621b9e5d0ea5203565cdAffected
  • a11b9f65eae766b17ec3451a6a1766f0a9d1dbff to before f2db71053dc0409fae785096ad19cce4c8a95af7Affected
LinuxLinux
  • 4.10Affected
  • before 4.10Not 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.