All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+48fbe2f8fdcd2fbc1242@syzkaller.appspotmail.com>
To: andreyknvl@google.com, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: BUG: bad host encryption descriptor; descriptor is too short (0 vs 5 needed)
Date: Mon, 28 Oct 2019 06:02:09 -0700	[thread overview]
Message-ID: <000000000000835f920595f81bfa@google.com> (raw)

Hello,

syzbot found the following crash on:

HEAD commit:    22be26f7 usb-fuzzer: main usb gadget fuzzer driver
git tree:       https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=16eccc0f600000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5fe29bc39eff9627
dashboard link: https://syzkaller.appspot.com/bug?extid=48fbe2f8fdcd2fbc1242
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10d08e4ce00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11fb07ff600000

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+48fbe2f8fdcd2fbc1242@syzkaller.appspotmail.com

usb 1-1: config 0 interface 66 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=40.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.66: Wire Adapter v125.52 newer than groked v1.0
hwa-hc 1-1:0.66: FIXME: USB_MAXCHILDREN too low for WUSB adapter (53 ports)
usb 1-1: BUG: bad host encryption descriptor; descriptor is too short (0 vs  
5 needed)
usb 1-1: supported encryption types: ����|�������
usb 1-1: E: host doesn't support CCM-1 crypto
hwa-hc 1-1:0.66: Cannot initialize internals: -19


---
This bug 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@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches

             reply	other threads:[~2019-10-28 13:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 13:02 syzbot [this message]
2019-11-19 14:41 ` BUG: bad host encryption descriptor; descriptor is too short (0 vs 5 needed) Andrey Konovalov

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=000000000000835f920595f81bfa@google.com \
    --to=syzbot+48fbe2f8fdcd2fbc1242@syzkaller.appspotmail.com \
    --cc=andreyknvl@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.