linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: Greg KH <greg@kroah.com>,
	syzbot <syzbot+d934a9036346e0215d8f@syzkaller.appspotmail.com>
Cc: andreyknvl@google.com, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: BUG: bad host security descriptor; not enough data (4 vs 5 left)
Date: Wed, 20 Nov 2019 12:18:57 +0100	[thread overview]
Message-ID: <1574248737.14298.33.camel@suse.com> (raw)
In-Reply-To: <20191111160950.GA870254@kroah.com>

Am Montag, den 11.11.2019, 17:09 +0100 schrieb Greg KH:
> On Mon, Nov 11, 2019 at 07:34:08AM -0800, syzbot wrote:
> > Hello,
> > 
> > syzbot found the following crash on:
> > 
> > HEAD commit:    3183c037 usb: gadget: add raw-gadget interface
> > git tree:       https://github.com/google/kasan.git usb-fuzzer
> > console output: https://syzkaller.appspot.com/x/log.txt?x=12525dc6e00000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=79de80330003b5f7
> > dashboard link: https://syzkaller.appspot.com/bug?extid=d934a9036346e0215d8f
> > compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14ac7406e00000
> > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13eea39ae00000
> > 
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+d934a9036346e0215d8f@syzkaller.appspotmail.com
> > 
> > usb 1-1: config 0 interface 0 altsetting 0 has 3 endpoint descriptors,
> > different from the interface descriptor's value: 4
> > usb 1-1: New USB device found, idVendor=13dc, idProduct=5611,
> > bcdDevice=2f.15
> > usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > usb 1-1: config 0 descriptor??
> > hwa-hc 1-1:0.0: Wire Adapter v106.52 newer than groked v1.0
> > hwa-hc 1-1:0.0: FIXME: USB_MAXCHILDREN too low for WUSB adapter (194 ports)
> > usb 1-1: BUG: bad host security descriptor; not enough data (4 vs 5 left)
> > usb 1-1: supported encryption types: �S\x03Ё���|c\x03Ё����c\x03Ё���
> > usb 1-1: E: host doesn't support CCM-1 crypto
> > hwa-hc 1-1:0.0: Wireless USB HWA host controller
> > hwa-hc 1-1:0.0: new USB bus registered, assigned bus number 11
> 
> wusb code, hah.  It's about to be deleted from the kernel because no one
> uses it and there is no hardware out there.  I wouldn't spend a ton of
> time fuzzing it.
> 
> One more good reason to just delete it soon...

Unfortunately that is not an option for the stable trees. Before I try
something quick and dirty here, I have a question for the testing team.

What exactly crashed? There is nothing in the logs? Did you undergo
an absolute freeze of the machine? Or do you tested for the word "BUG"
in the logs?

	Regards
		Oliver


  reply	other threads:[~2019-11-20 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11 15:34 BUG: bad host security descriptor; not enough data (4 vs 5 left) syzbot
2019-11-11 16:09 ` Greg KH
2019-11-20 11:18   ` Oliver Neukum [this message]
2019-11-20 11:24     ` Dmitry Vyukov
2019-11-20 13:32     ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1574248737.14298.33.camel@suse.com \
    --to=oneukum@suse.com \
    --cc=andreyknvl@google.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=syzbot+d934a9036346e0215d8f@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).