From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: edumazet@google.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: Tue, 23 May 2023 18:47:41 +0200 [thread overview]
Message-ID: <CAHmME9pEu2cvrSQd+Rg8Cp=KDfKEfjeiPPgF-WecXLHyRZVjcw@mail.gmail.com> (raw)
In-Reply-To: <20230523094606.6f4f8f4f@kernel.org>
On Tue, May 23, 2023 at 6:46 PM Jakub Kicinski <kuba@kernel.org> wrote:
>
> On Tue, 23 May 2023 18:14:18 +0200 Jason A. Donenfeld wrote:
> > So, IOW, not a wireguard bug, right?
>
> What's slightly concerning is that there aren't any other timers
> leading to
>
> KASAN: slab-use-after-free Write in enqueue_timer
>
> :( If WG was just an innocent bystander there should be, right?
Well, WG does mod this timer for every single packet in its RX path.
So that's bound to turn things up I suppose.
next prev parent reply other threads:[~2023-05-23 16:54 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
2023-05-23 16:14 ` Jason A. Donenfeld
2023-05-23 16:46 ` Jakub Kicinski
2023-05-23 16:47 ` Jason A. Donenfeld [this message]
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='CAHmME9pEu2cvrSQd+Rg8Cp=KDfKEfjeiPPgF-WecXLHyRZVjcw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jann@thejh.net \
--cc=kuba@kernel.org \
--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).