syzbot

 sign-in | mailing list | source | docs
🐞 Open [819]
🐞 Fixed [75]
🐞 Invalid [980]
⬇ Missing Backports [121]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

UBSAN: array-index-out-of-bounds in dbAllocBits

Status: upstream: reported C repro on 2023/05/19 07:30
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+76c960a839deb49a86ec@syzkaller.appspotmail.com
First crash: 837d, last: 28d
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Bug presence (1)
Date Name Commit Repro Result
2024/11/02 upstream (ToT) 11066801dd4b C [report] UBSAN: array-index-out-of-bounds in dbAllocBits
▶ ▼ Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream UBSAN: array-index-out-of-bounds in dbAllocBits jfs 19 C inconclusive error 234 613d 1064d 0/29 auto-obsoleted due to no activity on 2024/03/07 21:48
upstream KASAN: slab-out-of-bounds Read in dbAllocBits jfs 17 C error 257 4d09h 481d 0/29 upstream: reported C repro on 2024/05/09 13:18
linux-6.1 UBSAN: array-index-out-of-bounds in dbAllocBits origin:upstream 15 C error 2 354d 837d 0/3 upstream: reported C repro on 2023/05/19 04:28
linux-4.19 KASAN: use-after-free Read in dbAllocBits 19 C error 2 1045d 1067d 0/1 upstream: reported C repro on 2022/10/01 12:57
▶ ▼ Last patch testing requests (7)
Created Duration User Patch Repo Result
2025/08/04 20:04 10m retest repro linux-5.15.y report log
2025/08/04 20:04 12m retest repro linux-5.15.y report log
2025/07/17 04:43 12m retest repro linux-5.15.y report log
2025/05/25 09:05 1h09m retest repro linux-5.15.y report log
2025/05/07 00:07 10m retest repro linux-5.15.y report log
2025/03/12 03:57 8m retest repro linux-5.15.y report log
2025/02/25 01:13 14m retest repro linux-5.15.y report log

Sample crash report:
loop0: detected capacity change from 0 to 32768
================================================================================
UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:2306:2
index 2000 is out of range for type 's64[128]' (aka 'long long[128]')
CPU: 1 PID: 3504 Comm: syz-executor422 Not tainted 5.15.117-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 ubsan_epilogue lib/ubsan.c:151 [inline]
 __ubsan_handle_out_of_bounds+0x118/0x140 lib/ubsan.c:282
 dbAllocBits+0x961/0x990 fs/jfs/jfs_dmap.c:2306
 dbAllocDmap fs/jfs/jfs_dmap.c:2083 [inline]
 dbAllocNear+0x262/0x390 fs/jfs/jfs_dmap.c:1312
 dbAlloc+0xa1f/0xc90 fs/jfs/jfs_dmap.c:829
 ea_get+0x9b5/0x1280 fs/jfs/xattr.c:514
 __jfs_setxattr+0x4b6/0x11d0 fs/jfs/xattr.c:718
 __jfs_set_acl+0x12a/0x1b0 fs/jfs/acl.c:87
 jfs_set_acl+0x2a9/0x550 fs/jfs/acl.c:114
 set_posix_acl fs/posix_acl.c:947 [inline]
 posix_acl_xattr_set+0x33b/0x3a0 fs/posix_acl.c:966
 __vfs_setxattr+0x3e7/0x420 fs/xattr.c:182
 __vfs_setxattr_noperm+0x12a/0x5e0 fs/xattr.c:216
 vfs_setxattr+0x21d/0x420 fs/xattr.c:303
 do_setxattr fs/xattr.c:588 [inline]
 setxattr+0x27e/0x2e0 fs/xattr.c:611
 path_setxattr+0x1bc/0x2a0 fs/xattr.c:630
 __do_sys_lsetxattr fs/xattr.c:653 [inline]
 __se_sys_lsetxattr fs/xattr.c:649 [inline]
 __x64_sys_lsetxattr+0xb4/0xd0 fs/xattr.c:649
 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:0x7efe84c2e849
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffec9de64c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000bd
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007efe84c2e849
RDX: 0000000020000180 RSI: 0000000020000040 RDI: 0000000020000000
RBP: 00007efe84bee0e0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000024 R11: 0000000000000246 R12: 00007efe84bee170
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
================================================================================

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/06/17 04:22 linux-5.15.y 471e639e59d1 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan UBSAN: array-index-out-of-bounds in dbAllocBits
2025/07/21 09:37 linux-5.15.y c79648372d02 7117feec .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan-arm64 UBSAN: array-index-out-of-bounds in dbAllocBits
2023/05/19 07:29 linux-5.15.y 9d6bde853685 3bb7af1d .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 UBSAN: array-index-out-of-bounds in dbAllocBits
2025/07/21 08:30 linux-5.15.y c79648372d02 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 UBSAN: array-index-out-of-bounds in dbAllocBits
2025/07/21 08:29 linux-5.15.y c79648372d02 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 UBSAN: array-index-out-of-bounds in dbAllocBits
* Struck through repros no longer work on HEAD.