CVE-2022-49738

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix to do sanity check on i_extra_isize in is_alive()<br /> <br /> syzbot found a f2fs bug:<br /> <br /> BUG: KASAN: slab-out-of-bounds in data_blkaddr fs/f2fs/f2fs.h:2891 [inline]<br /> BUG: KASAN: slab-out-of-bounds in is_alive fs/f2fs/gc.c:1117 [inline]<br /> BUG: KASAN: slab-out-of-bounds in gc_data_segment fs/f2fs/gc.c:1520 [inline]<br /> BUG: KASAN: slab-out-of-bounds in do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734<br /> Read of size 4 at addr ffff888076557568 by task kworker/u4:3/52<br /> <br /> CPU: 1 PID: 52 Comm: kworker/u4:3 Not tainted 6.1.0-rc4-syzkaller-00362-gfef7fd48922d #0<br /> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022<br /> Workqueue: writeback wb_workfn (flush-7:0)<br /> Call Trace:<br /> <br /> __dump_stack lib/dump_stack.c:88 [inline]<br /> dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106<br /> print_address_description mm/kasan/report.c:284 [inline]<br /> print_report+0x15e/0x45d mm/kasan/report.c:395<br /> kasan_report+0xbb/0x1f0 mm/kasan/report.c:495<br /> data_blkaddr fs/f2fs/f2fs.h:2891 [inline]<br /> is_alive fs/f2fs/gc.c:1117 [inline]<br /> gc_data_segment fs/f2fs/gc.c:1520 [inline]<br /> do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734<br /> f2fs_gc+0x88c/0x20a0 fs/f2fs/gc.c:1831<br /> f2fs_balance_fs+0x544/0x6b0 fs/f2fs/segment.c:410<br /> f2fs_write_inode+0x57e/0xe20 fs/f2fs/inode.c:753<br /> write_inode fs/fs-writeback.c:1440 [inline]<br /> __writeback_single_inode+0xcfc/0x1440 fs/fs-writeback.c:1652<br /> writeback_sb_inodes+0x54d/0xf90 fs/fs-writeback.c:1870<br /> wb_writeback+0x2c5/0xd70 fs/fs-writeback.c:2044<br /> wb_do_writeback fs/fs-writeback.c:2187 [inline]<br /> wb_workfn+0x2dc/0x12f0 fs/fs-writeback.c:2227<br /> process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289<br /> worker_thread+0x665/0x1080 kernel/workqueue.c:2436<br /> kthread+0x2e4/0x3a0 kernel/kthread.c:376<br /> ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306<br /> <br /> The root cause is that we forgot to do sanity check on .i_extra_isize<br /> in below path, result in accessing invalid address later, fix it.<br /> - gc_data_segment<br /> - is_alive<br /> - data_blkaddr<br /> - offset_in_addr