{"vulnerability": "CVE-2024-56692", "sightings": [{"uuid": "def4ca84-2200-434b-95ea-8f977ee108d6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56692", "type": "seen", "source": "https://t.me/cvedetector/13841", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56692 - \"F2FS Linux Kernel F2fs Block Address Corruption Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-56692 \nPublished : Dec. 28, 2024, 10:15 a.m. | 45\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nf2fs: fix to do sanity check on node blkaddr in truncate_node()  \n  \nsyzbot reports a f2fs bug as below:  \n  \n------------[ cut here ]------------  \nkernel BUG at fs/f2fs/segment.c:2534!  \nRIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534  \nCall Trace:  \n truncate_node+0x1ae/0x8c0 fs/f2fs/node.c:909  \n f2fs_remove_inode_page+0x5c2/0x870 fs/f2fs/node.c:1288  \n f2fs_evict_inode+0x879/0x15c0 fs/f2fs/inode.c:856  \n evict+0x4e8/0x9b0 fs/inode.c:723  \n f2fs_handle_failed_inode+0x271/0x2e0 fs/f2fs/inode.c:986  \n f2fs_create+0x357/0x530 fs/f2fs/namei.c:394  \n lookup_open fs/namei.c:3595 [inline]  \n open_last_lookups fs/namei.c:3694 [inline]  \n path_openat+0x1c03/0x3590 fs/namei.c:3930  \n do_filp_open+0x235/0x490 fs/namei.c:3960  \n do_sys_openat2+0x13e/0x1d0 fs/open.c:1415  \n do_sys_open fs/open.c:1430 [inline]  \n __do_sys_openat fs/open.c:1446 [inline]  \n __se_sys_openat fs/open.c:1441 [inline]  \n __x64_sys_openat+0x247/0x2a0 fs/open.c:1441  \n do_syscall_x64 arch/x86/entry/common.c:52 [inline]  \n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  \n entry_SYSCALL_64_after_hwframe+0x77/0x7f  \nRIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534  \n  \nThe root cause is: on a fuzzed image, blkaddr in nat entry may be  \ncorrupted, then it will cause system panic when using it in  \nf2fs_invalidate_blocks(), to avoid this, let's add sanity check on  \nnat blkaddr in truncate_node(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-28T12:06:09.000000Z"}, {"uuid": "be7ec565-45df-4ed0-ba4b-64bd61a0232c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-56692", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "c2efc7c8-09c0-4556-b245-327c83139772", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56692", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "3b2b59f5-038b-473f-9c33-8ad8d693541d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56692", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3leebixrxwm22", "content": "", "creation_timestamp": "2024-12-28T10:16:03.849179Z"}, {"uuid": "107b184e-62be-4530-9ae1-a07d6f8d6bcb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56692", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113730073602107423", "content": "", "creation_timestamp": "2024-12-28T10:53:23.779418Z"}]}