From: Jakub Kicinski <kuba@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Eric Dumazet <edumazet@google.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
syzbot <syzbot+c2775460db0e1c70018e@syzkaller.appspotmail.com>,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
davem@davemloft.net, linux-kernel@vger.kernel.org,
pabeni@redhat.com, wireguard@lists.zx2c4.com, jann@thejh.net
Subject: Re: [syzbot] [wireguard?] KASAN: slab-use-after-free Write in enqueue_timer
Date: Wed, 24 May 2023 08:39:35 -0700 [thread overview]
Message-ID: <20230524083935.7108f17f@kernel.org> (raw)
In-Reply-To: <20230524083341.0cd435f7@kernel.org>
On Wed, 24 May 2023 08:33:41 -0700 Jakub Kicinski wrote:
> On Wed, 24 May 2023 10:24:31 +0200 Dmitry Vyukov wrote:
> > FWIW There are more report examples on the dashboard.
> > There are some that don't mention wireguard nor usbnet, e.g.:
> > https://syzkaller.appspot.com/text?tag=CrashReport&x=17dd2446280000
> > So that's probably red herring. But they all seem to mention alloc_netdev_mqs.
>
> While we have you, let me ask about the possibility of having vmcore
> access - I think it'd be very useful to solve this mystery.
> With a bit of luck the timer still has the function set.
I take that back.
Memory state around the buggy address:
ffff88801ecc1400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff88801ecc1480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88801ecc1500: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff88801ecc1580: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff88801ecc1600: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
next prev parent reply other threads:[~2023-05-24 15:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 18:01 syzbot
2023-05-23 15:46 ` Jason A. Donenfeld
2023-05-23 16:05 ` Jakub Kicinski
2023-05-23 16:12 ` Eric Dumazet
2023-05-23 16:41 ` Jakub Kicinski
2023-05-23 16:42 ` Jason A. Donenfeld
2023-05-23 16:47 ` Jakub Kicinski
2023-05-23 17:01 ` Jason A. Donenfeld
2023-05-23 17:05 ` Eric Dumazet
2023-05-23 17:07 ` Eric Dumazet
2023-05-24 8:24 ` Dmitry Vyukov
2023-05-24 15:33 ` Jakub Kicinski
2023-05-24 15:39 ` Jakub Kicinski [this message]
2023-05-23 16:14 ` Jason A. Donenfeld
2023-05-23 16:46 ` Jakub Kicinski
2023-05-23 16:47 ` Jason A. Donenfeld
2023-05-23 17:16 ` Jason A. Donenfeld
2023-05-23 17:28 ` Jason A. Donenfeld
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=20230524083935.7108f17f@kernel.org \
--to=kuba@kernel.org \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=jann@thejh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+c2775460db0e1c70018e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wireguard@lists.zx2c4.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).