syzbot

 sign-in | mailing list | source | docs
🐞 Open [700]
🐞 Fixed [72]
🐞 Invalid [878]
⬇ Missing Backports [111]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

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
Labels: missing-backport
[Documentation on labels]
Reported-by: syzbot+72da154e9f7c4866295f@syzkaller.appspotmail.com
First crash: 487d, last: 3d01h
▶ ▼ Bug presence (3)
Date Name Commit Repro Result
2024/12/11 linux-5.15.y (ToT) 0a51d2d4527b C [report] KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list
2024/01/28 upstream (ToT) 8a696a29c690 C [report] KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list
2024/12/11 upstream (ToT) f92f4749861b C Didn't crash
▶ ▼ 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 missing-backport C done 3 152d 738d 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 513d 944d 25/28 fixed on 2024/02/16 19:40
linux-5.15 KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list 3 692d 768d 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 830d 942d 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 862d 945d 0/1 upstream: reported C repro on 2022/10/28 06:50
▶ ▼ Last patch testing requests (7)
Created Duration User Patch Repo Result
2025/05/11 10:29 11m retest repro linux-5.15.y report log
2025/04/18 00:43 10m retest repro linux-5.15.y report log
2025/02/19 22:58 8m retest repro linux-5.15.y report log
2025/02/06 20:08 18m retest repro linux-5.15.y report log
2025/01/22 09:31 11m retest repro linux-5.15.y report log
2024/10/21 10:31 30m retest repro linux-5.15.y report log
2024/10/05 21:31 15m retest repro linux-5.15.y report log
▶ ▼ Fix bisection attempts (8)
Created Duration User Patch Repo Result
2025/04/25 22:26 1h39m bisect fix linux-5.15.y OK (0) job log log
2025/03/22 17:33 1h18m bisect fix linux-5.15.y OK (0) job log log
2024/11/28 18:57 58m bisect fix linux-5.15.y OK (0) job log log
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): checking transaction log (loop0)
REISERFS (device loop0): Using tea hash to sort names
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
==================================================================
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-executor416/4161

CPU: 1 PID: 4161 Comm: syz-executor416 Not tainted 5.15.175-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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_older_commits fs/reiserfs/journal.c:919 [inline]
 flush_commit_list+0x497/0x1ec0 fs/reiserfs/journal.c:995
 do_journal_end+0x3bb3/0x4650 fs/reiserfs/journal.c:4372
 reiserfs_sync_fs+0xca/0x140 fs/reiserfs/super.c:78
 sync_filesystem+0x1bc/0x220 fs/sync.c:66
 generic_shutdown_super+0x6b/0x310 fs/super.c:448
 kill_block_super+0x7a/0xe0 fs/super.c:1427
 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:188
 exit_task_work include/linux/task_work.h:33 [inline]
 do_exit+0x6a3/0x2480 kernel/exit.c:874
 do_group_exit+0x144/0x310 kernel/exit.c:996
 __do_sys_exit_group kernel/exit.c:1007 [inline]
 __se_sys_exit_group kernel/exit.c:1005 [inline]
 __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1005
 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:0x7fdf733cfb89
Code: Unable to access opcode bytes at RIP 0x7fdf733cfb5f.
RSP: 002b:00007fff73722928 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fdf733cfb89
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007fdf7345d2d0 R08: ffffffffffffffb8 R09: 0000000000000006
R10: 0000000020013483 R11: 0000000000000246 R12: 00007fdf7345d2d0
R13: 0000000000000000 R14: 00007fdf7345e040 R15: 00007fdf7339e0d0
 </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
==================================================================

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/01/08 07:08 linux-5.15.y 91786f140358 f3558dbf .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/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
2025/05/27 10:37 linux-5.15.y 98f47d0e9b8c 874a1386 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan-arm64 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
2025/05/27 09:06 linux-5.15.y 98f47d0e9b8c 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list
* Struck through repros no longer work on HEAD.