linux-kernel - kernel panic: stack is corrupted in lock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 01 Sep 2019 16:27:06 -0700
From:   syzbot <syzbot+97deee97cf14574b96d0@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        syzkaller-bugs@...glegroups.com
Subject: kernel panic: stack is corrupted in lock_release (2)

Hello,

syzbot found the following crash on:

HEAD commit:    dd7078f0 enetc: Add missing call to 'pci_free_irq_vectors(..
git tree:       net
console output: https://syzkaller.appspot.com/x/log.txt?x=115fe0fa600000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2a6a2b9826fdadf9
dashboard link: https://syzkaller.appspot.com/bug?extid=97deee97cf14574b96d0
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11f7c2fe600000

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+97deee97cf14574b96d0@...kaller.appspotmail.com

Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in:  
lock_release+0x866/0x960 kernel/locking/lockdep.c:4435
CPU: 0 PID: 9965 Comm: syz-executor.0 Not tainted 5.3.0-rc6+ #182
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS  
Google 01/01/2011
Call Trace:
Kernel Offset: disabled
Rebooting in 86400 seconds..

---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@...glegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches