Answer in brief
CVE-2024-39467 records a High severity (CVSS 7.8) vulnerability in f2fs: fix to do sanity check on i_xattr_nid in sanity_check_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.
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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <c559a8d840562fbfce9f318448dda2f7d3e6d8e8 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <75c87e2ac6149abf44bdde0dd6d541763ddb0dff || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <1640dcf383cdba52be8b28d2a1a2aa7ef7a30c98 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <8c8aa473fe6eb46a4bf99f3ea2dbe52bf0c1a1f0 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <be0155202e431f3007778568a72432c68f8946ba || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <68e3cd4ecb8603936cccdc338929130045df2e57 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <20faaf30e55522bba2b56d9c46689233205d7717 | c559a8d840562fbfce9f318448dda2f7d3e6d8e8, 75c87e2ac6149abf44bdde0dd6d541763ddb0dff, 1640dcf383cdba52be8b28d2a1a2aa7ef7a30c98, 8c8aa473fe6eb46a4bf99f3ea2dbe52bf0c1a1f0, be0155202e431f3007778568a72432c68f8946ba, 68e3cd4ecb8603936cccdc338929130045df2e57, 20faaf30e55522bba2b56d9c46689233205d7717 |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Jun 25, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 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 i_xattr_nid in sanity_check_inode() syzbot reports a kernel bug as below: F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4 ================================================================== BUG: KASAN: slab-out-of-bounds in f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline] BUG: KASAN: slab-out-of-bounds in current_nat_addr fs/f2fs/node.h:213 [inline] BUG: KASAN: slab-out-of-bounds in f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600 Read of size 1 at addr ffff88807a58c76c by task syz-executor280/5076 CPU: 1 PID: 5076 Comm: syz-executor280 Not tainted 6.9.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline] current_nat_addr fs/f2fs/node.h:213 [inline] f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600 f2fs_xattr_fiemap fs/f2fs/data.c:1848 [inline] f2fs_fiemap+0x55d/0x1ee0 fs/f2fs/data.c:1925 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1c07/0x2e50 fs/ioctl.c:838 __do_sys_ioctl fs/ioctl.c:902 [inline] __se_sys_ioctl+0x81/0x170 fs/ioctl.c:890 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is we missed to do sanity check on i_xattr_nid during f2fs_iget(), so that in fiemap() path, current_nat_addr() will access nat_bitmap w/ offset from invalid i_xattr_nid, result in triggering kasan bug report, fix it.
Quoted source text, attributed separately from HOL analysis.