From: Dmitry Vyukov <dvyukov@google.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: syzbot <syzbot+b364ed862aa07c74bc62@syzkaller.appspotmail.com>,
David Miller <davem@davemloft.net>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
"open list:KERNEL BUILD + fi..." <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Michal Marek <mmarek@suse.com>, netdev <netdev@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: KASAN: use-after-free Write in hci_sock_release
Date: Mon, 25 Mar 2019 09:04:26 +0100 [thread overview]
Message-ID: <CACT4Y+b5T6x_crSRStNST-btPYDGzujZ=Q20RLpaJs=taLA9wg@mail.gmail.com> (raw)
In-Reply-To: <CAM_iQpVHgHM-5NCE+FNZfpH6CWtYdt8BSmHJj_oa7CLKxYKLQw@mail.gmail.com>
On Sat, Mar 23, 2019 at 9:25 PM Cong Wang <xiyou.wangcong@gmail.com> wrote:
>
> On Fri, Mar 22, 2019 at 5:19 AM Dmitry Vyukov <dvyukov@google.com> wrote:
> >
> > On Fri, Mar 22, 2019 at 1:04 PM syzbot
> > <syzbot+b364ed862aa07c74bc62@syzkaller.appspotmail.com> wrote:
> > >
> > > syzbot has bisected this bug to:
> > >
> > > commit c470abd4fde40ea6a0846a2beab642a578c0b8cd
> > > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > > Date: Sun Feb 19 22:34:00 2017 +0000
> > >
> > > Linux 4.10
> > >
> > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1664c6df200000
> > > start commit: c470abd4 Linux 4.10
> > > git tree: upstream
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=7308e68273924137
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=b364ed862aa07c74bc62
> > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=152532bb400000
> > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13f73320c00000
> > >
> > > Reported-by: syzbot+b364ed862aa07c74bc62@syzkaller.appspotmail.com
> > > Fixes: c470abd4fde4 ("Linux 4.10")
> > >
> > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> >
> > The same story of HCI being broken before v4.10, so this is bisected
> > to the release.
>
> Does syzbot test the latest upstream?
Yes, it does.
> Isn't this supposed to be fixed by
>
> commit e20a2e9c42c9e4002d9e338d74e7819e88d77162
> Author: Myungho Jung <mhjungk@gmail.com>
> Date: Sat Feb 2 16:56:36 2019 -0800
>
> Bluetooth: Fix decrementing reference count twice in releasing socket
>
> ?
I and syzbot have no idea. You may know better. Is it? If yes, please
tell syzbot about the fix.
next prev parent reply other threads:[~2019-03-25 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 14:38 KASAN: use-after-free Write in hci_sock_release syzbot
2019-01-04 9:27 ` syzbot
2019-03-22 12:04 ` syzbot
2019-03-22 12:16 ` Dmitry Vyukov
2019-03-23 20:25 ` Cong Wang
2019-03-25 8:04 ` Dmitry Vyukov [this message]
2020-05-16 21:27 ` 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='CACT4Y+b5T6x_crSRStNST-btPYDGzujZ=Q20RLpaJs=taLA9wg@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mmarek@suse.com \
--cc=netdev@vger.kernel.org \
--cc=syzbot+b364ed862aa07c74bc62@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@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 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).