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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3299fb36854f Linux 5.15.108
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16d6ed9fc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=108ad532b7717ab6
dashboard link: https://syzkaller.appspot.com/bug?extid=f2dfe4636342e2cbcf3b
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5f08ed196f7f/disk-3299fb36.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7f30a6b0d826/vmlinux-3299fb36.xz
kernel image: https://storage.googleapis.com/syzbot-assets/07102113a249/bzImage-3299fb36.xz

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

REISERFS warning (device loop4): jdm-20006 create_privroot: xattrs/ACLs enabled and couldn't find/create .reiserfs_priv. Failing mount.
==================================================================
BUG: KASAN: vmalloc-out-of-bounds in cleanup_bitmap_list+0x175/0x500 fs/reiserfs/journal.c:231
Read of size 8 at addr ffffc9000124c008 by task syz-executor.4/19159

CPU: 1 PID: 19159 Comm: syz-executor.4 Not tainted 5.15.108-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/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 fs/reiserfs/journal.c:1957 [inline]
journal_release_error+0x76/0x90 fs/reiserfs/journal.c:1975
reiserfs_fill_super+0x13e9/0x2690 fs/reiserfs/super.c:2227
mount_bdev+0x26d/0x3a0 fs/super.c:1378
legacy_get_tree+0xeb/0x180 fs/fs_context.c:610
vfs_get_tree+0x88/0x270 fs/super.c:1508
do_new_mount+0x28b/0xad0 fs/namespace.c:2994
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
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:0x7f7e8116c69a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7e7f6dcf88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00000000000010fe RCX: 00007f7e8116c69a
RDX: 0000000020001100 RSI: 0000000020001140 RDI: 00007f7e7f6dcfe0
RBP: 00007f7e7f6dd020 R08: 00007f7e7f6dd020 R09: 0000000000010048
R10: 0000000000010048 R11: 0000000000000202 R12: 0000000020001100
R13: 0000000020001140 R14: 00007f7e7f6dcfe0 R15: 0000000020000400
</TASK>


Memory state around the buggy address:
ffffc9000124bf00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
ffffc9000124bf80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
>ffffc9000124c000: 00 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
^
ffffc9000124c080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
ffffc9000124c100: 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.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.