CVE-2022-49380f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count()
- 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 avoid f2fs_bug_on() in dec_valid_node_count() As Yanming reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215897 I have encountered a bug in F2FS file system in kernel v5.17. The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by running the following commands: The kernel message is shown below: kernel BUG at fs/f2fs/f2fs.h:2511! Call Trace: f2fs_remove_inode_page+0x2a2/0x830 f2fs_evict_inode+0x9b7/0x1510 evict+0x282/0x4e0 do_unlinkat+0x33a/0x540 __x64_sys_unlinkat+0x8e/0xd0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is: .total_valid_block_count or .total_valid_node_count could fuzzed to zero, then once dec_valid_node_count() was called, it will cause BUG_ON(), this patch fixes to print warning info and set SBI_NEED_FSCK into CP instead of panic.
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 (18 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 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 – < f8b3c3fcf33105bc1ee7788e3b51b0a1ae42ae53
- affected 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 – < 2766ddaf45b69252bb8fe526b5b6e56904a9ae7a
- affected 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 – < bce859358d3d5940aa858e40ceee70ee6e76130e
- affected 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 – < 89d9a48d0cd30429463ea4e37ca83be6773ed5eb
- affected 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 – < ccffa99ae6a1f44797b57444c6a80382a42928fe
- affected 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 – < 4d17e6fe9293d57081ffdc11e1cf313e25e8fd9e
- affected 3.8
- unaffected < 3.8
- 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/f8b3c3fcf33105bc1ee7788e3b51b0a1ae42ae53 (opens in a new tab)
- https://git.kernel.org/stable/c/2766ddaf45b69252bb8fe526b5b6e56904a9ae7a (opens in a new tab)
- https://git.kernel.org/stable/c/bce859358d3d5940aa858e40ceee70ee6e76130e (opens in a new tab)
- https://git.kernel.org/stable/c/89d9a48d0cd30429463ea4e37ca83be6773ed5eb (opens in a new tab)
- https://git.kernel.org/stable/c/ccffa99ae6a1f44797b57444c6a80382a42928fe (opens in a new tab)
- https://git.kernel.org/stable/c/4d17e6fe9293d57081ffdc11e1cf313e25e8fd9e (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-54849 (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-49380)Record last updated .