syzbot


KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list (2)

Status: upstream: reported C repro on 2024/01/28 16:33
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+72da154e9f7c4866295f@syzkaller.appspotmail.com
First crash: 255d, last: 4d16h
Bug presence (1)
Date Name Commit Repro Result
2024/01/28 upstream (ToT) 8a696a29c690 C [report] KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list origin:upstream C 3 36d 506d 0/3 upstream: reported C repro on 2023/05/22 16:15
upstream KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list reiserfs C error done 100 281d 712d 25/28 fixed on 2024/02/16 19:40
linux-5.15 KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list 3 460d 536d 0/3 auto-obsoleted due to no activity on 2023/10/16 09:07
linux-4.14 BUG: unable to handle kernel paging request in cleanup_bitmap_list C 1 598d 710d 0/1 upstream: reported C repro on 2022/10/30 13:58
linux-4.19 BUG: unable to handle kernel paging request in cleanup_bitmap_list reiserfs C error 2 630d 713d 0/1 upstream: reported C repro on 2022/10/28 06:50
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/10/05 21:31 15m retest repro linux-5.15.y report log
Fix bisection attempts (5)
Created Duration User Patch Repo Result
2024/08/12 05:11 56m bisect fix linux-5.15.y OK (0) job log log
2024/06/30 17:22 1h46m bisect fix linux-5.15.y OK (0) job log log
2024/05/21 22:24 1h08m bisect fix linux-5.15.y OK (0) job log log
2024/04/06 22:58 1h44m bisect fix linux-5.15.y OK (0) job log log
2024/03/07 02:21 57m bisect fix linux-5.15.y OK (0) job log log

Sample crash report:
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 tea 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 ffffc90000e56008 by task syz-executor183/3565

CPU: 1 PID: 3565 Comm: syz-executor183 Not tainted 5.15.166-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2d0 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
 cleanup_freed_for_journal_list fs/reiserfs/journal.c:570 [inline]
 flush_commit_list+0x1636/0x1ec0 fs/reiserfs/journal.c:1139
 flush_journal_list+0x2a8/0x1c80 fs/reiserfs/journal.c:1388
 flush_used_journal_lists+0x1254/0x15d0 fs/reiserfs/journal.c:1826
 do_journal_end+0x391a/0x4650
 do_journal_begin_r+0x950/0x1000
 journal_begin+0x148/0x350 fs/reiserfs/journal.c:3253
 reiserfs_fill_super+0x1812/0x2690 fs/reiserfs/super.c:2108
 mount_bdev+0x2c9/0x3f0 fs/super.c:1398
 legacy_get_tree+0xeb/0x180 fs/fs_context.c:611
 vfs_get_tree+0x88/0x270 fs/super.c:1528
 do_new_mount+0x2ba/0xb40 fs/namespace.c:3005
 do_mount fs/namespace.c:3348 [inline]
 __do_sys_mount fs/namespace.c:3556 [inline]
 __se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3533
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f55316828ea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 5e 04 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f553163e088 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f553163e0a0 RCX: 00007f55316828ea
RDX: 0000000020001100 RSI: 0000000020001140 RDI: 00007f553163e0a0
RBP: 0000000000000004 R08: 00007f553163e0e0 R09: 00000000000010e7
R10: 0000000000000000 R11: 0000000000000286 R12: 00007f553163e0e0
R13: 0000000000000000 R14: 0000000000000003 R15: 0000000000400000
 </TASK>


Memory state around the buggy address:
 ffffc90000e55f00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
 ffffc90000e55f80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
>ffffc90000e56000: 00 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
                      ^
 ffffc90000e56080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
 ffffc90000e56100: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
==================================================================

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/09/09 02:07 linux-5.15.y 14e468424d3e 9750182a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list
2024/01/28 16:33 linux-5.15.y 6139f2a02fe0 cc4a4020 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list
2024/04/20 16:49 linux-5.15.y c52b9710c83d af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list
2024/04/07 04:43 linux-5.15.y 9465fef4ae35 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list
* Struck through repros no longer work on HEAD.