All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: andreyknvl@google.com,
	syzbot <syzbot+513e4d0985298538bf9b@syzkaller.appspotmail.com>
Cc: glider@google.com, <gregkh@linuxfoundation.org>,
	<gustavo@embeddedor.com>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>,
	<syzkaller-bugs@googlegroups.com>
Subject: Re: KMSAN: kernel-usb-infoleak in pcan_usb_pro_send_req
Date: Tue, 30 Jul 2019 10:17:19 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.1907301011100.1507-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <00000000000014c877058ee2c4a6@google.com>

On Tue, 30 Jul 2019, syzbot wrote:

> Hello,
> 
> syzbot found the following crash on:
> 
> HEAD commit:    41550654 [UPSTREAM] KVM: x86: degrade WARN to pr_warn_rate..
> git tree:       kmsan
> console output: https://syzkaller.appspot.com/x/log.txt?x=13e95183a00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=40511ad0c5945201
> dashboard link: https://syzkaller.appspot.com/bug?extid=513e4d0985298538bf9b
> compiler:       clang version 9.0.0 (/home/glider/llvm/clang  
> 80fee25776c2fb61e74c1ecb1a523375c2500b69)
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17eafa1ba00000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17b87983a00000
> 
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+513e4d0985298538bf9b@syzkaller.appspotmail.com
> 
> usb 1-1: config 0 has no interface number 0
> usb 1-1: New USB device found, idVendor=0c72, idProduct=0014,  
> bcdDevice=8b.53
> usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> usb 1-1: config 0 descriptor??
> peak_usb 1-1:0.146: PEAK-System PCAN-USB X6 v0 fw v0.0.0 (2 channels)
> ==================================================================
> BUG: KMSAN: kernel-usb-infoleak in usb_submit_urb+0x7ef/0x1f50  
> drivers/usb/core/urb.c:405

What does "kernel-usb-infoleak" mean?

Alan Stern


  reply	other threads:[~2019-07-30 14:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30  9:38 KMSAN: kernel-usb-infoleak in pcan_usb_pro_send_req syzbot
2019-07-30 14:17 ` Alan Stern [this message]
2019-07-30 14:20   ` Andrey Konovalov
2019-07-30 14:22     ` Andrey Konovalov
2019-07-30 14:28       ` Alexander Potapenko
2019-08-06 12:45 ` Oliver Neukum
2019-08-06 12:45   ` syzbot
2019-08-06 12:49   ` Andrey Konovalov
2019-08-06 13:59     ` Alan Stern
2019-08-06 14:00       ` Andrey Konovalov
2019-08-06 13:05 ` Oliver Neukum
2019-08-06 14:44   ` syzbot

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=Pine.LNX.4.44L0.1907301011100.1507-100000@iolanthe.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=andreyknvl@google.com \
    --cc=glider@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo@embeddedor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=syzbot+513e4d0985298538bf9b@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 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.