From: syzbot <syzbot+452e9465a3b2817fa4c2@syzkaller.appspotmail.com>
To: anant.thazhemadam@gmail.com, bobo.shaobowang@huawei.com,
cobranza@ingcoecuador.com, davem@davemloft.net,
ducheng2@gmail.com, johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.von.dentz@intel.com, marcel@holtmann.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: null-ptr-deref Write in l2cap_chan_put
Date: Fri, 26 Nov 2021 08:47:09 -0800 [thread overview]
Message-ID: <00000000000091c45705d1b3d7ea@google.com> (raw)
In-Reply-To: <0000000000000a389a05ac5a9864@google.com>
syzbot suspects this issue was fixed by commit:
commit 1bff51ea59a9afb67d2dd78518ab0582a54a472c
Author: Wang ShaoBo <bobo.shaobowang@huawei.com>
Date: Wed Sep 1 00:35:37 2021 +0000
Bluetooth: fix use-after-free error in lock_sock_nested()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=141cfa45b00000
start commit: c70672d8d316 Merge tag 's390-5.9-5' of git://git.kernel.or..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=bd46548257448703
dashboard link: https://syzkaller.appspot.com/bug?extid=452e9465a3b2817fa4c2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=152f31f9900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: fix use-after-free error in lock_sock_nested()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-11-26 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 9:46 KASAN: null-ptr-deref Write in l2cap_chan_put syzbot
2021-11-26 16:47 ` syzbot [this message]
2021-12-04 9:48 ` [syzbot] " Dmitry Vyukov
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=00000000000091c45705d1b3d7ea@google.com \
--to=syzbot+452e9465a3b2817fa4c2@syzkaller.appspotmail.com \
--cc=anant.thazhemadam@gmail.com \
--cc=bobo.shaobowang@huawei.com \
--cc=cobranza@ingcoecuador.com \
--cc=davem@davemloft.net \
--cc=ducheng2@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--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.