All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8a8429a8b80280ff1c80@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 security descriptor; not enough data (2 vs 5 left)
Date: Wed, 06 Nov 2019 04:32:10 -0800	[thread overview]
Message-ID: <000000000000d5795d0596acbc93@google.com> (raw)

Hello,

syzbot found the following crash on:

HEAD commit:    b1aa9d83 usb: raw: add raw-gadget interface
git tree:       https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=153a1f8ae00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=79de80330003b5f7
dashboard link: https://syzkaller.appspot.com/bug?extid=8a8429a8b80280ff1c80
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10893fcce00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15bbaa62e00000

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+8a8429a8b80280ff1c80@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=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.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 (2 vs 5 left)
usb 1-1: supported encryption types: ���|�������
usb 1-1: E: host doesn't support CCM-1 crypto
hwa-hc 1-1:0.0: 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-11-06 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 12:32 syzbot [this message]
2019-11-19 14:41 ` BUG: bad host security descriptor; not enough data (2 vs 5 left) 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=000000000000d5795d0596acbc93@google.com \
    --to=syzbot+8a8429a8b80280ff1c80@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.