CVE-2024-39467

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode()<br /> <br /> syzbot reports a kernel bug as below:<br /> <br /> F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4<br /> ==================================================================<br /> BUG: KASAN: slab-out-of-bounds in f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline]<br /> BUG: KASAN: slab-out-of-bounds in current_nat_addr fs/f2fs/node.h:213 [inline]<br /> BUG: KASAN: slab-out-of-bounds in f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600<br /> Read of size 1 at addr ffff88807a58c76c by task syz-executor280/5076<br /> <br /> CPU: 1 PID: 5076 Comm: syz-executor280 Not tainted 6.9.0-rc5-syzkaller #0<br /> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024<br /> Call Trace:<br /> <br /> __dump_stack lib/dump_stack.c:88 [inline]<br /> dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114<br /> print_address_description mm/kasan/report.c:377 [inline]<br /> print_report+0x169/0x550 mm/kasan/report.c:488<br /> kasan_report+0x143/0x180 mm/kasan/report.c:601<br /> f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline]<br /> current_nat_addr fs/f2fs/node.h:213 [inline]<br /> f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600<br /> f2fs_xattr_fiemap fs/f2fs/data.c:1848 [inline]<br /> f2fs_fiemap+0x55d/0x1ee0 fs/f2fs/data.c:1925<br /> ioctl_fiemap fs/ioctl.c:220 [inline]<br /> do_vfs_ioctl+0x1c07/0x2e50 fs/ioctl.c:838<br /> __do_sys_ioctl fs/ioctl.c:902 [inline]<br /> __se_sys_ioctl+0x81/0x170 fs/ioctl.c:890<br /> do_syscall_x64 arch/x86/entry/common.c:52 [inline]<br /> do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83<br /> entry_SYSCALL_64_after_hwframe+0x77/0x7f<br /> <br /> The root cause is we missed to do sanity check on i_xattr_nid during<br /> f2fs_iget(), so that in fiemap() path, current_nat_addr() will access<br /> nat_bitmap w/ offset from invalid i_xattr_nid, result in triggering<br /> kasan bug report, fix it.