netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+709b7a64d57978247e44@syzkaller.appspotmail.com>
To: davem@davemloft.net, f.fainelli@gmail.com, kuba@kernel.org,
	linux-kernel@vger.kernel.org, mkubecek@suse.cz,
	netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in ethnl_update_bitset32
Date: Mon, 24 Feb 2020 03:46:01 -0800	[thread overview]
Message-ID: <0000000000005b46ba059f50ea17@google.com> (raw)
In-Reply-To: <00000000000005efef059f4e27e1@google.com>

syzbot has bisected this bug to:

commit bfbcfe2032e70bd8598d680d39ac177d507e39ac
Author: Michal Kubecek <mkubecek@suse.cz>
Date:   Fri Dec 27 14:56:13 2019 +0000

    ethtool: set link modes related data with LINKMODES_SET request

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=16d59109e00000
start commit:   0c0ddd6a Merge tag 'linux-watchdog-5.6-rc3' of git://www.l..
git tree:       net
final crash:    https://syzkaller.appspot.com/x/report.txt?x=15d59109e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=11d59109e00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3b8906eb6a7d6028
dashboard link: https://syzkaller.appspot.com/bug?extid=709b7a64d57978247e44
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13885de9e00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1518127ee00000

Reported-by: syzbot+709b7a64d57978247e44@syzkaller.appspotmail.com
Fixes: bfbcfe2032e7 ("ethtool: set link modes related data with LINKMODES_SET request")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      reply	other threads:[~2020-02-24 11:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24  8:28 KASAN: use-after-free Read in ethnl_update_bitset32 syzbot
2020-02-24 11:46 ` 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=0000000000005b46ba059f50ea17@google.com \
    --to=syzbot+709b7a64d57978247e44@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkubecek@suse.cz \
    --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 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).