All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+5ec3d1378e31c88d87f4@syzkaller.appspotmail.com>
To: davem@davemloft.net, fgheet255t@gmail.com, hdanton@sina.com,
	kuba@kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, lukas@wunner.de,
	netdev@vger.kernel.org, oliver@neukum.org, oneukum@suse.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in cdc_ncm_tx_fixup
Date: Thu, 09 Jun 2022 05:23:13 -0700	[thread overview]
Message-ID: <000000000000b252fe05e102e228@google.com> (raw)
In-Reply-To: <000000000000e2fc6405d3061843@google.com>

syzbot suspects this issue was fixed by commit:

commit d1408f6b4dd78fb1b9e26bcf64477984e5f85409
Author: Lukas Wunner <lukas@wunner.de>
Date:   Thu May 12 08:42:01 2022 +0000

    usbnet: Run unregister_netdev() before unbind() again

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=122a4b57f00000
start commit:   330f4c53d3c2 ARM: fix build error when BPF_SYSCALL is disa..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=aba0ab2928a512c2
dashboard link: https://syzkaller.appspot.com/bug?extid=5ec3d1378e31c88d87f4
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=135ca155700000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: usbnet: Run unregister_netdev() before unbind() again

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

  parent reply	other threads:[~2022-06-09 12:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 12:20 [syzbot] KASAN: use-after-free Read in cdc_ncm_tx_fixup syzbot
2022-03-08  7:01 ` syzbot
2022-06-09 12:23 ` syzbot [this message]
     [not found] <20220308150836.3680-1-hdanton@sina.com>
2022-03-08 15:20 ` 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=000000000000b252fe05e102e228@google.com \
    --to=syzbot+5ec3d1378e31c88d87f4@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=fgheet255t@gmail.com \
    --cc=hdanton@sina.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=netdev@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=oneukum@suse.com \
    --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.