Answer in brief
CVE-2022-49361 records a Unknown severity vulnerability in f2fs: fix to do sanity check for inline 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 | >=fcc85a4d86b5018f08717160c89c0eb50afd1dca <efdefbe8b7564602ab446474788225a1f2a323b5 || >=fcc85a4d86b5018f08717160c89c0eb50afd1dca <7cfe2d43becaf76e562b9617d2c2d9b445f86761 || >=fcc85a4d86b5018f08717160c89c0eb50afd1dca <11c1cd032df85df3c096a57a7f27d57819956e4a || >=fcc85a4d86b5018f08717160c89c0eb50afd1dca <198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8 || >=fcc85a4d86b5018f08717160c89c0eb50afd1dca <677a82b44ebf263d4f9a0cfbd576a6ade797a07b | efdefbe8b7564602ab446474788225a1f2a323b5, 7cfe2d43becaf76e562b9617d2c2d9b445f86761, 11c1cd032df85df3c096a57a7f27d57819956e4a, 198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8, 677a82b44ebf263d4f9a0cfbd576a6ade797a07b |
| Linux/Linuxgeneric | 4.2 | 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 do sanity check for inline inode Yanming reported a kernel bug in Bugzilla kernel [1], which can be reproduced. The bug message is: The kernel message is shown below: kernel BUG at fs/inode.c:611! Call Trace: evict+0x282/0x4e0 __dentry_kill+0x2b2/0x4d0 dput+0x2dd/0x720 do_renameat2+0x596/0x970 __x64_sys_rename+0x78/0x90 do_syscall_64+0x3b/0x90 [1] https://bugzilla.kernel.org/show_bug.cgi?id=215895 The bug is due to fuzzed inode has both inline_data and encrypted flags. During f2fs_evict_inode(), as the inode was deleted by rename(), it will cause inline data conversion due to conflicting flags. The page cache will be polluted and the panic will be triggered in clear_inode(). Try fixing the bug by doing more sanity checks for inline data inode in sanity_check_inode().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-49361 records a Unknown severity vulnerability in f2fs: fix to do sanity check for inline 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 | >=fcc85a4d86b5018f08717160c89c0eb50afd1dca <efdefbe8b7564602ab446474788225a1f2a323b5 || >=fcc85a4d86b5018f08717160c89c0eb50afd1dca <7cfe2d43becaf76e562b9617d2c2d9b445f86761 || >=fcc85a4d86b5018f08717160c89c0eb50afd1dca <11c1cd032df85df3c096a57a7f27d57819956e4a || >=fcc85a4d86b5018f08717160c89c0eb50afd1dca <198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8 || >=fcc85a4d86b5018f08717160c89c0eb50afd1dca <677a82b44ebf263d4f9a0cfbd576a6ade797a07b | efdefbe8b7564602ab446474788225a1f2a323b5, 7cfe2d43becaf76e562b9617d2c2d9b445f86761, 11c1cd032df85df3c096a57a7f27d57819956e4a, 198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8, 677a82b44ebf263d4f9a0cfbd576a6ade797a07b |
| Linux/Linuxgeneric | 4.2 | 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 do sanity check for inline inode Yanming reported a kernel bug in Bugzilla kernel [1], which can be reproduced. The bug message is: The kernel message is shown below: kernel BUG at fs/inode.c:611! Call Trace: evict+0x282/0x4e0 __dentry_kill+0x2b2/0x4d0 dput+0x2dd/0x720 do_renameat2+0x596/0x970 __x64_sys_rename+0x78/0x90 do_syscall_64+0x3b/0x90 [1] https://bugzilla.kernel.org/show_bug.cgi?id=215895 The bug is due to fuzzed inode has both inline_data and encrypted flags. During f2fs_evict_inode(), as the inode was deleted by rename(), it will cause inline data conversion due to conflicting flags. The page cache will be polluted and the panic will be triggered in clear_inode(). Try fixing the bug by doing more sanity checks for inline data inode in sanity_check_inode().
Quoted source text, attributed separately from HOL analysis.