[v5.15] KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6139f2a02fe0 Linux 5.15.148
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1562bbefe80000
kernel config: https://syzkaller.appspot.com/x/.config?x=3292eb21c4b0adb2
dashboard link: https://syzkaller.appspot.com/bug?extid=72da154e9f7c4866295f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14eb6ea0180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1766e437e80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8d3c4f91e092/disk-6139f2a0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/34bd8a404e99/vmlinux-6139f2a0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f1cd1a0b0f50/bzImage-6139f2a0.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/d4ff517b0ee9/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+72da15...@syzkaller.appspotmail.com

REISERFS (device loop0): journal params: device loop0, size 512, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
REISERFS (device loop0): checking transaction log (loop0)
REISERFS (device loop0): Using r5 hash to sort names
==================================================================
BUG: KASAN: vmalloc-out-of-bounds in cleanup_bitmap_list+0x175/0x500 fs/reiserfs/journal.c:231
Read of size 8 at addr ffffc90000e36008 by task syz-executor290/3501

CPU: 0 PID: 3501 Comm: syz-executor290 Not tainted 5.15.148-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
print_address_description+0x63/0x3b0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0x16b/0x1c0 mm/kasan/report.c:451
cleanup_bitmap_list+0x175/0x500 fs/reiserfs/journal.c:231
free_list_bitmaps+0x48/0x1a0 fs/reiserfs/journal.c:249
free_journal_ram+0xf8/0x3f0 fs/reiserfs/journal.c:1884
do_journal_release+0x362/0x4d0 fs/reiserfs/journal.c:1957
journal_release+0x1b/0x30 fs/reiserfs/journal.c:1968
reiserfs_put_super+0x237/0x4b0 fs/reiserfs/super.c:616
generic_shutdown_super+0x136/0x2c0 fs/super.c:475
kill_block_super+0x7a/0xe0 fs/super.c:1414
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x6a3/0x2480 kernel/exit.c:872
do_group_exit+0x144/0x310 kernel/exit.c:994
__do_sys_exit_group kernel/exit.c:1005 [inline]
__se_sys_exit_group kernel/exit.c:1003 [inline]
__x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1003
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f305ee5a849
Code: Unable to access opcode bytes at RIP 0x7f305ee5a81f.
RSP: 002b:00007ffe232a32c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f305ee5a849
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007f305eed72d0 R08: ffffffffffffffb8 R09: 00007ffe232a33a0
R10: 00007ffe232a33a0 R11: 0000000000000246 R12: 00007f305eed72d0
R13: 0000000000000000 R14: 00007f305eed8040 R15: 00007f305ee28d80
</TASK>


Memory state around the buggy address:
ffffc90000e35f00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
ffffc90000e35f80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
>ffffc90000e36000: 00 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
^
ffffc90000e36080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
ffffc90000e36100: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
==================================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup