linux-kernel - [syzbot] WARNING: ODEBUG bug in corrupted (2)

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:   Mon, 31 May 2021 10:25:23 -0700
From:   syzbot <syzbot+a437546ec71b04dfb5ac@...kaller.appspotmail.com>
To:     keescook@...omium.org, linux-kernel@...r.kernel.org,
        miaoqinglang@...wei.com, qiang.zhang@...driver.com,
        swboyd@...omium.org, syzkaller-bugs@...glegroups.com,
        tglx@...utronix.de
Subject: [syzbot] WARNING: ODEBUG bug in corrupted (2)

Hello,

syzbot found the following issue on:

HEAD commit:    d7c5303f Merge tag 'net-5.13-rc4' of git://git.kernel.org/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=122fa2b5d00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=770708ea7cfd4916
dashboard link: https://syzkaller.appspot.com/bug?extid=a437546ec71b04dfb5ac
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=155e106bd00000

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

smsmdtv:smscore_start_device: set device mode failed , rc -22
smsusb:smsusb_init_device: smscore_start_device(...) failed
------------[ cut here ]------------
ODEBUG: free active (active state 0) object type: work_struct hint: do_submit_urb+0x0/0x3e0 drivers/media/usb/siano/smsusb.c:146
WARNING: CPU: 1 PID: 27 at lib/debugobjects.c:505 debug_print_object+0x16e/0x250 lib/debugobjects.c:505
Modules linked in:

---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches