kernel panic: stack is corrupted in lock_release

Status: closed as dup on 2019/01/04 11:20
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+bc3cd5b4c1f71fc3c65d@syzkaller.appspotmail.com
First crash: 2774d, last: 2770d
▶ ▼ Duplicate of
Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported
kernel panic: stack is corrupted in udp4_lib_lookup2 net 2 11 2774d 2771d
▶ ▼ Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel panic: stack is corrupted in lock_release (3) ntfs3 2 syz, C error unreliable 8 1021d 1410d 0/29 auto-obsoleted due to no activity on 2024/01/27 07:30
upstream kernel panic: stack is corrupted in lock_release (2) kernel 2 syz error error 27 2481d 2529d 0/29 auto-obsoleted due to no activity on 2022/09/01 14:45
upstream kernel panic: stack is corrupted in lock_release (4) 2 1 714d 714d 0/29 closed as invalid on 2024/09/13 08:06

Sample crash report:
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lock_release+0x98e/0xc40 kernel/locking/lockdep.c:3864
CPU: 1 PID: 5196 Comm: syz-executor2 Not tainted 4.20.0+ #9
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/01/04 13:40 upstream 96d4f267e40f 7da23925 .config console log report ci-upstream-kasan-gce-smack-root
2019/01/02 12:25 upstream 8e143b90e4d4 f0491811 .config console log report ci-upstream-kasan-gce-selinux-root
2019/01/02 01:07 upstream 28e8c4bc8eb4 3d85f48c .config console log report ci-upstream-kasan-gce-smack-root
2018/12/31 13:07 upstream 195303136f19 2b42fdc8 .config console log report ci-upstream-kasan-gce-root
* Struck through repros no longer work on HEAD.