linux-kernel - BUG: corrupted list in corrupted (3)

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:   Tue, 23 Jun 2020 12:37:16 -0700
From:   syzbot <syzbot+0b3de1d31a24da20947b@...kaller.appspotmail.com>
To:     akpm@...l.org, andreyknvl@...gle.com, keescook@...omium.org,
        linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
        paulmck@...nel.org, riel@...hat.com, rostedt@...dmis.org,
        syzkaller-bugs@...glegroups.com
Subject: BUG: corrupted list in corrupted (3)

Hello,

syzbot found the following crash on:

HEAD commit:    f8f02d5c USB: OTG: rename product list of devices
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=11bfddf1100000
kernel config:  https://syzkaller.appspot.com/x/.config?x=fbe5dc26525767f1
dashboard link: https://syzkaller.appspot.com/bug?extid=0b3de1d31a24da20947b
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11abf20d100000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17ea5a11100000

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

------------[ cut here ]------------
kernel BUG at lib/list_debug.c:26!


---
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