linux-kernel - Re: WARNING in 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171107163556.GA13964@kroah.com>
Date:   Tue, 7 Nov 2017 17:35:56 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     syzbot 
        <bot+50d191d34989b5aa28596b0a2cb20c96f3ca4650@...kaller.appspotmail.com>
Cc:     felipe.balbi@...ux.intel.com, krinkin.m.u@...il.com,
        linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
        syzkaller-bugs@...glegroups.com, tiwai@...e.de,
        vskrishn@...eaurora.org
Subject: Re: WARNING in usb_submit_urb

On Tue, Nov 07, 2017 at 08:11:13AM -0800, syzbot wrote:
> Hello,
> 
> syzkaller hit the following crash on
> 36ef71cae353f88fd6e095e2aaa3e5953af1685d
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
> C reproducer is attached
> syzkaller reproducer is attached. See https://goo.gl/kgGztJ
> for information about syzkaller reproducers

This is not a crash, you are doing a panic-on-warning, and you send
invalid data to the kernel and it warned about it properly and kept on
working :)

Perhaps maybe not a full WARN_ON() is to be done here?

thanks,

greg k-h