Answer in brief
CVE-2022-49363 records a High severity (CVSS 7.8) vulnerability in f2fs: fix to do sanity check on block address in f2fs_do_zero_range(). 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.
Answer in brief
CVE-2022-49363 records a High severity (CVSS 7.8) vulnerability in f2fs: fix to do sanity check on block address in f2fs_do_zero_range(). 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.
CVSS is 7.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <7361c9f2bd6a8f0cbb41cdea9aff04765ff23f67 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <a34d7b49894b0533222188a52e2958750f830efd || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <f2e1c38b5ac64eb1a16a89c52fb419409d12c25b || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <470493be19a5730ed432e3ac0f29a2ee7fc6c557 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <805b48b234a2803cb7daec7f158af12f0fbaefac || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <25f8236213a91efdf708b9d77e9e51b6fc3e141c | 7361c9f2bd6a8f0cbb41cdea9aff04765ff23f67, a34d7b49894b0533222188a52e2958750f830efd, f2e1c38b5ac64eb1a16a89c52fb419409d12c25b, 470493be19a5730ed432e3ac0f29a2ee7fc6c557, 805b48b234a2803cb7daec7f158af12f0fbaefac, 25f8236213a91efdf708b9d77e9e51b6fc3e141c |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on block address in f2fs_do_zero_range() As Yanming reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215894 I have encountered a bug in F2FS file system in kernel v5.17. I have uploaded the system call sequence as case.c, and a fuzzed image can be found in google net disk The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by running the following commands: kernel BUG at fs/f2fs/segment.c:2291! Call Trace: f2fs_invalidate_blocks+0x193/0x2d0 f2fs_fallocate+0x2593/0x4a70 vfs_fallocate+0x2a5/0xac0 ksys_fallocate+0x35/0x70 __x64_sys_fallocate+0x8e/0xf0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is, after image was fuzzed, block mapping info in inode will be inconsistent with SIT table, so in f2fs_fallocate(), it will cause panic when updating SIT with invalid blkaddr. Let's fix the issue by adding sanity check on block address before updating SIT table with it.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <7361c9f2bd6a8f0cbb41cdea9aff04765ff23f67 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <a34d7b49894b0533222188a52e2958750f830efd || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <f2e1c38b5ac64eb1a16a89c52fb419409d12c25b || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <470493be19a5730ed432e3ac0f29a2ee7fc6c557 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <805b48b234a2803cb7daec7f158af12f0fbaefac || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <25f8236213a91efdf708b9d77e9e51b6fc3e141c | 7361c9f2bd6a8f0cbb41cdea9aff04765ff23f67, a34d7b49894b0533222188a52e2958750f830efd, f2e1c38b5ac64eb1a16a89c52fb419409d12c25b, 470493be19a5730ed432e3ac0f29a2ee7fc6c557, 805b48b234a2803cb7daec7f158af12f0fbaefac, 25f8236213a91efdf708b9d77e9e51b6fc3e141c |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on block address in f2fs_do_zero_range() As Yanming reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215894 I have encountered a bug in F2FS file system in kernel v5.17. I have uploaded the system call sequence as case.c, and a fuzzed image can be found in google net disk The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by running the following commands: kernel BUG at fs/f2fs/segment.c:2291! Call Trace: f2fs_invalidate_blocks+0x193/0x2d0 f2fs_fallocate+0x2593/0x4a70 vfs_fallocate+0x2a5/0xac0 ksys_fallocate+0x35/0x70 __x64_sys_fallocate+0x8e/0xf0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is, after image was fuzzed, block mapping info in inode will be inconsistent with SIT table, so in f2fs_fallocate(), it will cause panic when updating SIT with invalid blkaddr. Let's fix the issue by adding sanity check on block address before updating SIT table with it.
Quoted source text, attributed separately from HOL analysis.