CVE-2022-49738 in Linux
Sumário
de VulDB • 24/05/2026
No kernel do Linux, a seguinte vulnerabilidade foi corrigida:
f2fs: correção para realizar verificação de integridade (sanity check) em i_extra_isize em is_alive()
O syzbot encontrou um bug no f2fs:
BUG: KASAN: slab-out-of-bounds em data_blkaddr fs/f2fs/f2fs.h:2891 [inline]
BUG: KASAN: slab-out-of-bounds em is_alive fs/f2fs/gc.c:1117 [inline]
BUG: KASAN: slab-out-of-bounds em gc_data_segment fs/f2fs/gc.c:1520 [inline]
BUG: KASAN: slab-out-of-bounds em do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734 Leitura de tamanho 4 no endereço ffff888076557568 pela tarefa kworker/u4:3/52
CPU: 1 PID: 52 Comm: kworker/u4:3 Não contaminado 6.1.0-rc4-syzkaller-00362-gfef7fd48922d #0 Nome do hardware: Google Google Compute Engine/Google Compute Engine, BIOS Google 26/10/2022 Workqueue: writeback wb_workfn (flush-7:0) Rastreamento de chamada (Call Trace):
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [inline]
print_report+0x15e/0x45d mm/kasan/report.c:395 kasan_report+0xbb/0x1f0 mm/kasan/report.c:495 data_blkaddr fs/f2fs/f2fs.h:2891 [inline]
is_alive fs/f2fs/gc.c:1117 [inline]
gc_data_segment fs/f2fs/gc.c:1520 [inline]
do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734 f2fs_gc+0x88c/0x20a0 fs/f2fs/gc.c:1831 f2fs_balance_fs+0x544/0x6b0 fs/f2fs/segment.c:410 f2fs_write_inode+0x57e/0xe20 fs/f2fs/inode.c:753 write_inode fs/fs-writeback.c:1440 [inline]
__writeback_single_inode+0xcfc/0x1440 fs/fs-writeback.c:1652 writeback_sb_inodes+0x54d/0xf90 fs/fs-writeback.c:1870 wb_writeback+0x2c5/0xd70 fs/fs-writeback.c:2044 wb_do_writeback fs/fs-writeback.c:2187 [inline]
wb_workfn+0x2dc/0x12f0 fs/fs-writeback.c:2227 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e4/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
A causa raiz é que esquecemos de fazer a verificação de integridade (sanity check) em .i_extra_isize no caminho abaixo, resultando no acesso a um endereço inválido posteriormente, corrigir isso. - gc_data_segment - is_alive - data_blkaddr - offset_in_addr
If you want to get the best quality for vulnerability data then you always have to consider VulDB.