CVE-2022-49364f2fs: fix to clear dirty inode in f2fs_evict_inode()
- 5.5MediumCVSS base score
- 0.26%Exploitation in 30 daysEPSS · top 82% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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]
Timeline
ID reserved
By Linux
Published
- 18 months later
· 18 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.26% · top 82% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected a11b9f65eae766b17ec3451a6a1766f0a9d1dbff – < 54c116615c99e22aa08aa950757ed726e2f60821
- affected a11b9f65eae766b17ec3451a6a1766f0a9d1dbff – < ccd58045beb997544b94558a9156be4742628491
- affected a11b9f65eae766b17ec3451a6a1766f0a9d1dbff – < c9196d21359be8c7ee231029d13682273925fd00
- affected a11b9f65eae766b17ec3451a6a1766f0a9d1dbff – < 03c9373b15fa1c245ec99b2b5e7ba209eae4ef42
- affected a11b9f65eae766b17ec3451a6a1766f0a9d1dbff – < c469953917b319d415fd621b9e5d0ea5203565cd
- affected a11b9f65eae766b17ec3451a6a1766f0a9d1dbff – < f2db71053dc0409fae785096ad19cce4c8a95af7
- affected 4.10
- unaffected < 4.10
- unaffected 5.4.198 – ≤ 5.4.*
- unaffected 5.10.121 – ≤ 5.10.*
- unaffected 5.15.46 – ≤ 5.15.*
- unaffected 5.17.14 – ≤ 5.17.*
- unaffected 5.18.3 – ≤ 5.18.*
- unaffected 5.19 – ≤ *
References
References6
- https://git.kernel.org/stable/c/54c116615c99e22aa08aa950757ed726e2f60821 (opens in a new tab)
- https://git.kernel.org/stable/c/ccd58045beb997544b94558a9156be4742628491 (opens in a new tab)
- https://git.kernel.org/stable/c/c9196d21359be8c7ee231029d13682273925fd00 (opens in a new tab)
- https://git.kernel.org/stable/c/03c9373b15fa1c245ec99b2b5e7ba209eae4ef42 (opens in a new tab)
- https://git.kernel.org/stable/c/c469953917b319d415fd621b9e5d0ea5203565cd (opens in a new tab)
- https://git.kernel.org/stable/c/f2db71053dc0409fae785096ad19cce4c8a95af7 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-54865 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-49364)Record last updated .