syzbot

 sign-in | mailing list | source | docs
🐞 Open [89]
🐞 Fixed [277]
🐞 Invalid [849]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

panic: malloc: allocation too large, type = NUM, size = ADDR (4)

Status: upstream: reported on 2025/02/07 03:03
Reported-by: syzbot+ad6862768dc0eea6581b@syzkaller.appspotmail.com
First crash: 15d, last: 4h24m
▶ ▼ Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
openbsd panic: malloc: allocation too large, type = NUM, size = ADDR (2) 126 94d 184d 0/3 auto-obsoleted due to no activity on 2025/01/09 10:32
openbsd panic: malloc: allocation too large, type = NUM, size = ADDR (3) 58 16d 19d 3/3 fixed on 2025/02/06 06:14
openbsd panic: malloc: allocation too large, type = NUM, size = ADDR C 3 1165d 1166d 3/3 fixed on 2021/12/21 15:21

Sample crash report:
panic: malloc: allocation too large, type = 31, size = 4294970988
Starting stack trace...
panic(ffffffff8336a83a) at panic+0x1d0 sys/kern/subr_prf.c:229
malloc(100000e6c,1f,1) at malloc+0xcf4 sys/kern/kern_malloc.c:334
sys_semop(ffff8000ffff7210,ffff8000360c8700,ffff8000360c8650) at sys_semop+0x234 sys/kern/sysv_sem.c:564
syscall(ffff8000360c8700) at syscall+0xb08 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff8000360c8700) at syscall+0xb08 sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xe24668299b0, count: 252
End of stack trace.

Crashes (10):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/02/22 16:30 openbsd 45a541306066 d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: malloc: allocation too large, type = NUM, size = ADDR
2025/02/13 06:46 openbsd eb8501b6f1f9 2afad16e .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: malloc: allocation too large, type = NUM, size = ADDR
2025/02/12 19:00 openbsd 705b70e045d6 b27c2402 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: malloc: allocation too large, type = NUM, size = ADDR
2025/02/12 18:15 openbsd 705b70e045d6 b27c2402 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: malloc: allocation too large, type = NUM, size = ADDR
2025/02/12 15:08 openbsd 705b70e045d6 b27c2402 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: malloc: allocation too large, type = NUM, size = ADDR
2025/02/09 21:30 openbsd d2e1daa0feb7 ef44b750 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: malloc: allocation too large, type = NUM, size = ADDR
2025/02/09 19:53 openbsd d2e1daa0feb7 ef44b750 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: malloc: allocation too large, type = NUM, size = ADDR
2025/02/09 18:39 openbsd d2e1daa0feb7 ef44b750 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: malloc: allocation too large, type = NUM, size = ADDR
2025/02/09 18:25 openbsd d2e1daa0feb7 ef44b750 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: malloc: allocation too large, type = NUM, size = ADDR
2025/02/07 03:02 openbsd 3dd691bf9970 53657d1b .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: malloc: allocation too large, type = NUM, size = ADDR
* Struck through repros no longer work on HEAD.