From: shuah <shuah@kernel.org>
To: syzbot <syzbot+600b03e0cf1b73bb23c4@syzkaller.appspotmail.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, syzkaller-bugs@googlegroups.com,
valentina.manea.m@gmail.com, shuah <shuah@kernel.org>
Subject: Re: KASAN: use-after-free Read in vhci_hub_control
Date: Thu, 7 Nov 2019 09:54:12 -0700 [thread overview]
Message-ID: <e312222f-d24e-ad18-1801-e266d6497a6a@kernel.org> (raw)
In-Reply-To: <000000000000c460630596c1d40d@google.com>
On 11/7/19 6:42 AM, syzbot wrote:
> syzbot suspects this bug was fixed by commit:
>
> commit 81f7567c51ad97668d1c3a48e8ecc482e64d4161
> Author: Shuah Khan (Samsung OSG) <shuah@kernel.org>
> Date: Fri Oct 5 22:17:44 2018 +0000
>
> usb: usbip: Fix BUG: KASAN: slab-out-of-bounds in vhci_hub_control()
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14046c2c600000
> start commit: 420f51f4 Merge tag 'arm64-fixes' of
> git://git.kernel.org/p..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=531a917630d2a492
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=600b03e0cf1b73bb23c4
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1116710a400000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=119be4ea400000
>
> If the result looks correct, please mark the bug fixed by replying with:
>
> #syz fix: usb: usbip: Fix BUG: KASAN: slab-out-of-bounds in
> vhci_hub_control()
>
> For information about bisection process see:
> https://goo.gl/tpsmEJ#bisection
>
#syz fix: usb: usbip: Fix BUG: KASAN: slab-out-of-bounds in
vhci_hub_control()
prev parent reply other threads:[~2019-11-07 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 9:21 KASAN: use-after-free Read in vhci_hub_control syzbot
2019-11-07 13:42 ` syzbot
2019-11-07 16:54 ` shuah [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=e312222f-d24e-ad18-1801-e266d6497a6a@kernel.org \
--to=shuah@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=syzbot+600b03e0cf1b73bb23c4@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=valentina.manea.m@gmail.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.