linux-kernel - Re: WARNING in corrupted/usb_submit

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-prev] [day] [month] [year] [list]

Date:   Wed, 13 Jan 2021 10:53:57 -0500
From:   Alan Stern <stern@...land.harvard.edu>
To:     syzbot <syzbot+4feb9bb7280fb554f021@...kaller.appspotmail.com>
Cc:     eli.billauer@...il.com, gregkh@...uxfoundation.org,
        gustavoars@...nel.org, ingrassia@...genesys.com,
        linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
        syzkaller-bugs@...glegroups.com, tiwai@...e.de
Subject: Re: WARNING in corrupted/usb_submit_urb (2)

On Tue, Jan 12, 2021 at 09:20:10PM -0800, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
> 
> commit c318840fb2a42ce25febc95c4c19357acf1ae5ca
> Author: Alan Stern <stern@...land.harvard.edu>
> Date:   Wed Dec 30 16:20:44 2020 +0000
> 
>     USB: Gadget: dummy-hcd: Fix shift-out-of-bounds bug
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17a8972f500000
> start commit:   cd796ed3 Merge tag 'trace-v5.10-rc7' of git://git.kernel.o..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=59df2a4dced5f928
> dashboard link: https://syzkaller.appspot.com/bug?extid=4feb9bb7280fb554f021
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1653b8a7500000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=170d946b500000
> 
> If the result looks correct, please mark the issue as fixed by replying with:
> 
> #syz fix: USB: Gadget: dummy-hcd: Fix shift-out-of-bounds bug
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection

I strongly believe that syzbot's conclusion is wrong.  The commit it 
identified has nothing to do with the original problem.

Alan Stern