cbcvebase.
CVE-2022-49364
published 2025-02-26

CVE-2022-49364: 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…

PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.26%
17.3th percentile
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]

Affected

17 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 5.18.5-1 (bookworm)linux 5.18.5-1 (bookworm)
linuxlinux——
linuxlinux>= 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < 54c116615c99e22aa08aa950757ed726e2f6082154c116615c99e22aa08aa950757ed726e2f60821
linuxlinux>= 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < ccd58045beb997544b94558a9156be4742628491ccd58045beb997544b94558a9156be4742628491
linuxlinux>= 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < c9196d21359be8c7ee231029d13682273925fd00c9196d21359be8c7ee231029d13682273925fd00
linuxlinux>= 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < 03c9373b15fa1c245ec99b2b5e7ba209eae4ef4203c9373b15fa1c245ec99b2b5e7ba209eae4ef42
linuxlinux>= 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < c469953917b319d415fd621b9e5d0ea5203565cdc469953917b319d415fd621b9e5d0ea5203565cd
linuxlinux>= 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < f2db71053dc0409fae785096ad19cce4c8a95af7f2db71053dc0409fae785096ad19cce4c8a95af7
linuxlinux_kernel>= 0 < 5.10.127-15.10.127-1
linuxlinux_kernel>= 0 < 5.18.5-15.18.5-1
linuxlinux_kernel>= 0 < 5.18.5-15.18.5-1
linuxlinux_kernel>= 0 < 5.18.5-15.18.5-1
linuxlinux_kernel>= 3.8 < 5.4.1985.4.198
linuxlinux_kernel>= 5.11 < 5.15.465.15.46
linuxlinux_kernel>= 5.16 < 5.17.145.17.14
linuxlinux_kernel>= 5.18 < 5.18.35.18.3
linuxlinux_kernel>= 5.5 < 5.10.1215.10.121

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.