syzbot

 sign-in | mailing list | source | docs
🐞 Open [1286]
≡ Subsystems
🐞 Fixed [5725]
🐞 Invalid [13964]
⬇ Missing Backports [95]
Kernel Health Bugs/Month Bug Lifetimes Fuzzing Crashes
Total Repo Heatmap Subsystems Heatmap
💬 Send us feedback

kernel panic: stack is corrupted in lock_acquire (3)

Status: closed as invalid on 2024/09/13 10:29
First crash: 54d, last: 54d
▶ ▼ Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel panic: stack is corrupted in lock_acquire kernel 2 2109d 2111d 0/28 closed as dup on 2019/01/04 11:23
upstream kernel panic: stack is corrupted in lock_acquire (2) ntfs3 C error done 27 380d 752d 0/28 auto-obsoleted due to no activity on 2024/01/14 06:22
linux-5.15 kernel panic: stack is corrupted in lock_acquire origin:upstream missing-backport C error 20 47d 514d 0/3 upstream: reported C repro on 2023/05/20 12:30
linux-6.1 kernel panic: stack is corrupted in lock_acquire 1 542d 542d 0/3 auto-obsoleted due to no activity on 2023/08/20 17:52

Sample crash report:
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lock_acquire+0x53e/0x550
Shutting down cpus with NMI
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/08/22 17:12 linux-next 6a7917c89f21 295a4b50 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in lock_acquire
* Struck through repros no longer work on HEAD.