Answer in brief
CVE-2024-56692 records a High severity (CVSS 7.8) vulnerability in f2fs: fix to do sanity check on node blkaddr in truncate_node(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), 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), 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 <27d6e7eff07f8cce8e83b162d8f21a07458c860d || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <c1077078ce4589b5e5387f6b0aaa0d4534b9eb57 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <0a5c8b3fbf6200f1c66062d307c9a52084917788 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <6babe00ccd34fc65b78ef8b99754e32b4385f23d | 27d6e7eff07f8cce8e83b162d8f21a07458c860d, c1077078ce4589b5e5387f6b0aaa0d4534b9eb57, 0a5c8b3fbf6200f1c66062d307c9a52084917788, 6babe00ccd34fc65b78ef8b99754e32b4385f23d |
| Linux/Linuxgeneric | 3.8 | Not reported |
| Linux/Linuxgeneric | >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <a6d51de6bf729edc9fc7f87ffaae4e6bbda6329a || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <27d6e7eff07f8cce8e83b162d8f21a07458c860d || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <c1077078ce4589b5e5387f6b0aaa0d4534b9eb57 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <0a5c8b3fbf6200f1c66062d307c9a52084917788 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <6babe00ccd34fc65b78ef8b99754e32b4385f23d | a6d51de6bf729edc9fc7f87ffaae4e6bbda6329a, 27d6e7eff07f8cce8e83b162d8f21a07458c860d, c1077078ce4589b5e5387f6b0aaa0d4534b9eb57, 0a5c8b3fbf6200f1c66062d307c9a52084917788, 6babe00ccd34fc65b78ef8b99754e32b4385f23d |
Published upstream
Dec 28, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on node blkaddr in truncate_node() syzbot reports a f2fs bug as below: ------------[ cut here ]------------ kernel BUG at fs/f2fs/segment.c:2534! RIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534 Call Trace: truncate_node+0x1ae/0x8c0 fs/f2fs/node.c:909 f2fs_remove_inode_page+0x5c2/0x870 fs/f2fs/node.c:1288 f2fs_evict_inode+0x879/0x15c0 fs/f2fs/inode.c:856 evict+0x4e8/0x9b0 fs/inode.c:723 f2fs_handle_failed_inode+0x271/0x2e0 fs/f2fs/inode.c:986 f2fs_create+0x357/0x530 fs/f2fs/namei.c:394 lookup_open fs/namei.c:3595 [inline] open_last_lookups fs/namei.c:3694 [inline] path_openat+0x1c03/0x3590 fs/namei.c:3930 do_filp_open+0x235/0x490 fs/namei.c:3960 do_sys_openat2+0x13e/0x1d0 fs/open.c:1415 do_sys_open fs/open.c:1430 [inline] __do_sys_openat fs/open.c:1446 [inline] __se_sys_openat fs/open.c:1441 [inline] __x64_sys_openat+0x247/0x2a0 fs/open.c:1441 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534 The root cause is: on a fuzzed image, blkaddr in nat entry may be corrupted, then it will cause system panic when using it in f2fs_invalidate_blocks(), to avoid this, let's add sanity check on nat blkaddr in truncate_node().
Quoted source text, attributed separately from HOL analysis.