From: syzbot <syzbot+a06c3db558cbb33d7ff9@syzkaller.appspotmail.com>
To: johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org,
stephen.s.brennan@oracle.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] KASAN: use-after-free Read in h4_recv_buf
Date: Wed, 15 Sep 2021 02:51:06 -0700 [thread overview]
Message-ID: <0000000000000e753105cc05a31d@google.com> (raw)
In-Reply-To: <000000000000a5339205c9e53883@google.com>
syzbot suspects this issue was fixed by commit:
commit 0766ec82e5fb26fc5dc6d592bc61865608bdc651
Author: Stephen Brennan <stephen.s.brennan@oracle.com>
Date: Wed Sep 1 17:51:41 2021 +0000
namei: Fix use after free in kern_path_locked
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14b29973300000
start commit: 7c60610d4767 Linux 5.14-rc6
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f61012d0b1cd846f
dashboard link: https://syzkaller.appspot.com/bug?extid=a06c3db558cbb33d7ff9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=147f96ee300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=112b3629300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: namei: Fix use after free in kern_path_locked
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-09-15 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 8:20 [syzbot] KASAN: use-after-free Read in h4_recv_buf syzbot
2021-09-15 9:51 ` syzbot [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=0000000000000e753105cc05a31d@google.com \
--to=syzbot+a06c3db558cbb33d7ff9@syzkaller.appspotmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=stephen.s.brennan@oracle.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).