From: syzbot <syzbot+db4869ba599c0de9b13e@syzkaller.appspotmail.com>
To: bst@pengutronix.de, davem@davemloft.net,
dev.kurt@vandijck-laurijssen.be, ecathinds@gmail.com,
kernel@pengutronix.de, linux-can@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@rempel-privat.de,
lkp@intel.com, maxime.jayat@mobile-devices.fr,
mkl@pengutronix.de, netdev@vger.kernel.org,
o.rempel@pengutronix.de, robin@protonic.nl,
socketcan@hartkopp.net, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in j1939_xtp_rx_abort_one
Date: Mon, 13 Jan 2020 08:42:02 -0800 [thread overview]
Message-ID: <000000000000a0ef18059c082789@google.com> (raw)
In-Reply-To: <0000000000005ed7710596937e86@google.com>
syzbot suspects this bug was fixed by commit:
commit ddeeb7d4822ed06d79fc15e822b70dce3fa77e39
Author: Oleksij Rempel <o.rempel@pengutronix.de>
Date: Sat Nov 9 15:11:18 2019 +0000
can: j1939: j1939_can_recv(): add priv refcounting
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15a7ec76e00000
start commit: de620fb9 Merge branch 'for-5.4-fixes' of git://git.kernel...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f9ff8f11e66c1fb1
dashboard link: https://syzkaller.appspot.com/bug?extid=db4869ba599c0de9b13e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=113e0d72e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=136aa6e8e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: can: j1939: j1939_can_recv(): add priv refcounting
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-01-13 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 6:25 KASAN: use-after-free Read in j1939_xtp_rx_abort_one syzbot
2019-11-05 21:30 ` syzbot
2019-11-06 2:43 ` syzbot
2020-01-13 16:42 ` syzbot [this message]
2020-01-17 12:26 ` Oleksij Rempel
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=000000000000a0ef18059c082789@google.com \
--to=syzbot+db4869ba599c0de9b13e@syzkaller.appspotmail.com \
--cc=bst@pengutronix.de \
--cc=davem@davemloft.net \
--cc=dev.kurt@vandijck-laurijssen.be \
--cc=ecathinds@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=lkp@intel.com \
--cc=maxime.jayat@mobile-devices.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robin@protonic.nl \
--cc=socketcan@hartkopp.net \
--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.