Answer in brief
CVE-2022-49380 records a Unknown severity vulnerability in f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count(). 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 | >=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <f8b3c3fcf33105bc1ee7788e3b51b0a1ae42ae53 || >=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <2766ddaf45b69252bb8fe526b5b6e56904a9ae7a || >=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <bce859358d3d5940aa858e40ceee70ee6e76130e || >=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <89d9a48d0cd30429463ea4e37ca83be6773ed5eb || >=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <ccffa99ae6a1f44797b57444c6a80382a42928fe || >=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <4d17e6fe9293d57081ffdc11e1cf313e25e8fd9e | f8b3c3fcf33105bc1ee7788e3b51b0a1ae42ae53, 2766ddaf45b69252bb8fe526b5b6e56904a9ae7a, bce859358d3d5940aa858e40ceee70ee6e76130e, 89d9a48d0cd30429463ea4e37ca83be6773ed5eb, ccffa99ae6a1f44797b57444c6a80382a42928fe, 4d17e6fe9293d57081ffdc11e1cf313e25e8fd9e |
| Linux/Linuxgeneric | 3.8 | 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 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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-49380 records a Unknown severity vulnerability in f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count(). 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 | >=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <f8b3c3fcf33105bc1ee7788e3b51b0a1ae42ae53 || >=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <2766ddaf45b69252bb8fe526b5b6e56904a9ae7a || >=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <bce859358d3d5940aa858e40ceee70ee6e76130e || >=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <89d9a48d0cd30429463ea4e37ca83be6773ed5eb || >=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <ccffa99ae6a1f44797b57444c6a80382a42928fe || >=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <4d17e6fe9293d57081ffdc11e1cf313e25e8fd9e | f8b3c3fcf33105bc1ee7788e3b51b0a1ae42ae53, 2766ddaf45b69252bb8fe526b5b6e56904a9ae7a, bce859358d3d5940aa858e40ceee70ee6e76130e, 89d9a48d0cd30429463ea4e37ca83be6773ed5eb, ccffa99ae6a1f44797b57444c6a80382a42928fe, 4d17e6fe9293d57081ffdc11e1cf313e25e8fd9e |
| Linux/Linuxgeneric | 3.8 | 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 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.
Quoted source text, attributed separately from HOL analysis.