cveboard RSS feed

CVE-2022-49364

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2022
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

f2fs: fix to clear dirty inode in f2fs_evict_inode()

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]

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
a11b9f65eae766b17ec3451a6a1766f0a9d1dbffaffectedgit54c116615c99e22aa08aa950757ed726e2f60821UnavailableNone listed
a11b9f65eae766b17ec3451a6a1766f0a9d1dbffaffectedgitccd58045beb997544b94558a9156be4742628491UnavailableNone listed
a11b9f65eae766b17ec3451a6a1766f0a9d1dbffaffectedgitc9196d21359be8c7ee231029d13682273925fd00UnavailableNone listed
a11b9f65eae766b17ec3451a6a1766f0a9d1dbffaffectedgit03c9373b15fa1c245ec99b2b5e7ba209eae4ef42UnavailableNone listed
a11b9f65eae766b17ec3451a6a1766f0a9d1dbffaffectedgitc469953917b319d415fd621b9e5d0ea5203565cdUnavailableNone listed
a11b9f65eae766b17ec3451a6a1766f0a9d1dbffaffectedgitf2db71053dc0409fae785096ad19cce4c8a95af7UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
4.10affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver4.10UnavailableNone listed
5.4.198unaffectedsemverUnavailable5.4.*None listed
5.10.121unaffectedsemverUnavailable5.10.*None listed
5.15.46unaffectedsemverUnavailable5.15.*None listed
5.17.14unaffectedsemverUnavailable5.17.*None listed
5.18.3unaffectedsemverUnavailable5.18.*None listed
5.19unaffectedoriginal_commit_for_fixUnavailable*None listed