All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Oliver Neukum <oneukum@suse.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	USB list <linux-usb@vger.kernel.org>,
	linux-scsi@vger.kernel.org, usb-storage@lists.one-eyed-alien.net,
	LKML <linux-kernel@vger.kernel.org>,
	Dmitry Vyukov <dvyukov@google.com>,
	Kostya Serebryany <kcc@google.com>,
	syzkaller <syzkaller@googlegroups.com>
Subject: Re: usb/storage/uas: slab-out-of-bounds in uas_probe
Date: Thu, 21 Sep 2017 18:10:27 +0200	[thread overview]
Message-ID: <20170921161027.GB15554@kroah.com> (raw)
In-Reply-To: <CAAeHK+xiFr1RW+HkoFhnypcgsnp6DgwzwVZ1pzQdzHeYZU+N5A@mail.gmail.com>

On Thu, Sep 21, 2017 at 05:39:05PM +0200, Andrey Konovalov wrote:
> Hi!
> 
> I've got the following report while fuzzing the kernel with syzkaller.
> 
> On commit ebb2c2437d8008d46796902ff390653822af6cc4 (Sep 18).
> 
> The issue occurs when we iterate over interface altsettings, but I
> don't see the driver doing anything wrong. I might be missing
> something, or this might be an issue in USB core altsettings parsing.


Any chance you happen to have the descriptors that you were feeding into
the kernel at this crash?  That might help in figuring out what "went
wrong".

thanks,

greg k-h

  reply	other threads:[~2017-09-21 16:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 15:39 usb/storage/uas: slab-out-of-bounds in uas_probe Andrey Konovalov
2017-09-21 16:10 ` Greg Kroah-Hartman [this message]
2017-09-21 16:24   ` Andrey Konovalov
2017-09-21 19:04     ` Alan Stern
2017-09-21 19:04       ` Alan Stern
2017-09-22  7:58       ` Greg Kroah-Hartman
2017-09-22  8:09         ` Greg Kroah-Hartman
2017-09-22 14:58           ` Alan Stern
2017-09-22 14:58             ` Alan Stern
2017-09-22 11:37       ` Andrey Konovalov
2017-09-22 11:37         ` Andrey Konovalov
2017-09-21 16:50 ` Alan Stern
2017-09-21 16:50   ` Alan Stern
2017-09-21 17:16   ` 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=20170921161027.GB15554@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreyknvl@google.com \
    --cc=dvyukov@google.com \
    --cc=kcc@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=stern@rowland.harvard.edu \
    --cc=syzkaller@googlegroups.com \
    --cc=usb-storage@lists.one-eyed-alien.net \
    /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.