Answer in brief
CVE-2022-49364 records a Unknown severity vulnerability in f2fs: fix to clear dirty inode in f2fs_evict_inode(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a11b9f65eae766b17ec3451a6a1766f0a9d1dbff <54c116615c99e22aa08aa950757ed726e2f60821 || >=a11b9f65eae766b17ec3451a6a1766f0a9d1dbff <ccd58045beb997544b94558a9156be4742628491 || >=a11b9f65eae766b17ec3451a6a1766f0a9d1dbff <c9196d21359be8c7ee231029d13682273925fd00 || >=a11b9f65eae766b17ec3451a6a1766f0a9d1dbff <03c9373b15fa1c245ec99b2b5e7ba209eae4ef42 || >=a11b9f65eae766b17ec3451a6a1766f0a9d1dbff <c469953917b319d415fd621b9e5d0ea5203565cd || >=a11b9f65eae766b17ec3451a6a1766f0a9d1dbff <f2db71053dc0409fae785096ad19cce4c8a95af7 | 54c116615c99e22aa08aa950757ed726e2f60821, ccd58045beb997544b94558a9156be4742628491, c9196d21359be8c7ee231029d13682273925fd00, 03c9373b15fa1c245ec99b2b5e7ba209eae4ef42, c469953917b319d415fd621b9e5d0ea5203565cd, f2db71053dc0409fae785096ad19cce4c8a95af7 |
| Linux/Linuxgeneric | 4.10 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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]
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-49364 records a Unknown severity vulnerability in f2fs: fix to clear dirty inode in f2fs_evict_inode(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a11b9f65eae766b17ec3451a6a1766f0a9d1dbff <54c116615c99e22aa08aa950757ed726e2f60821 || >=a11b9f65eae766b17ec3451a6a1766f0a9d1dbff <ccd58045beb997544b94558a9156be4742628491 || >=a11b9f65eae766b17ec3451a6a1766f0a9d1dbff <c9196d21359be8c7ee231029d13682273925fd00 || >=a11b9f65eae766b17ec3451a6a1766f0a9d1dbff <03c9373b15fa1c245ec99b2b5e7ba209eae4ef42 || >=a11b9f65eae766b17ec3451a6a1766f0a9d1dbff <c469953917b319d415fd621b9e5d0ea5203565cd || >=a11b9f65eae766b17ec3451a6a1766f0a9d1dbff <f2db71053dc0409fae785096ad19cce4c8a95af7 | 54c116615c99e22aa08aa950757ed726e2f60821, ccd58045beb997544b94558a9156be4742628491, c9196d21359be8c7ee231029d13682273925fd00, 03c9373b15fa1c245ec99b2b5e7ba209eae4ef42, c469953917b319d415fd621b9e5d0ea5203565cd, f2db71053dc0409fae785096ad19cce4c8a95af7 |
| Linux/Linuxgeneric | 4.10 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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]
Quoted source text, attributed separately from HOL analysis.