linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Konovalov <andreyknvl@google.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: syzbot <syzbot+22ae4e3b9fcc8a5c153a@syzkaller.appspotmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	LKML <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: KASAN: use-after-free Read in usb_kill_urb
Date: Mon, 12 Aug 2019 14:03:57 +0200	[thread overview]
Message-ID: <CAAeHK+ztV==ojaqueEzM4O5Bq_qdxVKhg8stvgT-VdMEs8GBtw@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1908091646230.1630-100000@iolanthe.rowland.org>

On Fri, Aug 9, 2019 at 10:52 PM Alan Stern <stern@rowland.harvard.edu> wrote:
>
> On Fri, 9 Aug 2019, syzbot wrote:
>
> > Hello,
> >
> > syzbot has tested the proposed patch and the reproducer did not trigger
> > crash:
> >
> > Reported-and-tested-by:
> > syzbot+22ae4e3b9fcc8a5c153a@syzkaller.appspotmail.com
> >
> > Tested on:
> >
> > commit:         e96407b4 usb-fuzzer: main usb gadget fuzzer driver
> > git tree:       https://github.com/google/kasan.git
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=cfa2c18fb6a8068e
> > compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> > patch:          https://syzkaller.appspot.com/x/patch.diff?x=173f2d2c600000
> >
> > Note: testing is done by a robot and is best-effort only.
>
> This shows that this bug is a duplicate of extid=30cf45ebfe0b0c4847a1.

Let's mark it as one:

#syz dup: KASAN: use-after-free Read in ld_usb_release

I'll also mark all bugs that involve ldusb as duplicates, as they all
likely are.

> This fact is also visible in the console logs; both have lines saying
> something like:
>
> [  549.416341][   T22] sysfs: cannot create duplicate filename '/class/usbmisc/ldusb0'
>
> and
>
> [  549.958755][   T22] ldusb 1-1:0.28: Not able to get a minor for this device.
>
> preceding the invalid access.
>
> Alan Stern
>

      reply	other threads:[~2019-08-12 12:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 17:48 KASAN: use-after-free Read in usb_kill_urb syzbot
2019-08-09 18:44 ` Prashant Malani
2019-08-09 19:00   ` Alan Stern
2019-08-09 19:26 ` Alan Stern
2019-08-09 19:46   ` syzbot
2019-08-09 20:52     ` Alan Stern
2019-08-12 12:03       ` Andrey Konovalov [this message]

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='CAAeHK+ztV==ojaqueEzM4O5Bq_qdxVKhg8stvgT-VdMEs8GBtw@mail.gmail.com' \
    --to=andreyknvl@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo@embeddedor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=syzbot+22ae4e3b9fcc8a5c153a@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).