syzbot

 sign-in | mailing list | source | docs
🐞 Open [1476]
≡ Subsystems
🐞 Fixed [6702]
🐞 Invalid [17194]
⬇ Missing Backports [217]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
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: 438d, last: 438d
▶ ▼ Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 kernel panic: stack is corrupted in lock_acquire (2) 2 2 332d 332d 0/3 auto-obsoleted due to no activity on 2025/03/16 12:34
upstream kernel panic: stack is corrupted in lock_acquire kernel 2 2 2493d 2495d 0/29 closed as dup on 2019/01/04 11:23
upstream kernel panic: stack is corrupted in lock_acquire (2) ntfs3 2 C error done 27 765d 1136d 0/29 auto-obsoleted due to no activity on 2024/01/14 06:22
linux-5.15 kernel panic: stack is corrupted in lock_acquire missing-backport origin:upstream 2 C inconclusive 20 162d 898d 0/3 auto-obsoleted due to no activity on 2025/09/06 10:25
linux-6.1 kernel panic: stack is corrupted in lock_acquire 2 1 926d 926d 0/3 auto-obsoleted due to no activity on 2023/08/20 17:52
upstream kernel panic: stack is corrupted in lock_acquire (4) cgroups mm 2 1 316d 312d 0/29 auto-obsoleted due to no activity on 2025/03/22 17:13

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.