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: <CAAeHK+y11k5rj9n=+Z7Y9bYjsWBoqaXfsystF3pCWgTPaRxrjg@mail.gmail.com>
Date:   Mon, 12 Oct 2020 14:58:34 +0200
From:   Andrey Konovalov <andreyknvl@...gle.com>
To:     Alan Stern <stern@...land.harvard.edu>
Cc:     syzbot <syzbot+f5378bcf0f0cab45c1c6@...kaller.appspotmail.com>,
        QCA ath9k Development <ath9k-devel@....qualcomm.com>,
        eli.billauer@...il.com,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        gustavoars@...nel.org, ingrassia@...genesys.com,
        LKML <linux-kernel@...r.kernel.org>,
        USB list <linux-usb@...r.kernel.org>,
        Oliver Neukum <oneukum@...e.com>,
        linux-wireless@...r.kernel.org,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        Takashi Iwai <tiwai@...e.de>
Subject: Re: WARNING in hif_usb_send/usb_submit_urb

On Fri, Oct 9, 2020 at 8:55 PM Alan Stern <stern@...land.harvard.edu> wrote:
>
> To the ath9k_htc maintainers:
>
> This is an attempt to fix a bug detected by the syzbot fuzzer.  The bug
> arises when a USB device claims to be an ATH9K but doesn't have the
> expected endpoints.  (In this case there was a bulk endpoint where the
> driver expected an interrupt endpoint.)  The kernel needs to be able to
> handle such devices without getting an internal error.
>
> On Fri, Oct 09, 2020 at 07:19:19AM -0700, syzbot wrote:
> > syzbot has found a reproducer for the following issue on:
> >
> > HEAD commit:    6c8cf369 usb: typec: Add QCOM PMIC typec detection driver
>
> Andrey, why doesn't syzbot put a 12-digit commit ID here?

No particular reason, I think. Makes sense to change it to 12, as it's
the recommended minimum AFAIU. I've a bug to track this here:
https://github.com/google/syzkaller/issues/2184

Thank you!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ