Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	syzbot <syzbot+96eb4e0d727f0ae998a6@syzkaller.appspotmail.com>
Cc: broonie@kernel.org, davem@davemloft.net, edumazet@google.com,
	jfs-discussion@lists.sourceforge.net, kuba@kernel.org,
	kuninori.morimoto.gx@renesas.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	pabeni@redhat.com, povik+lin@cutebit.org,
	syzkaller-bugs@googlegroups.com, wireguard@lists.zx2c4.com
Subject: Re: [syzbot] [wireguard?] [jfs?] KASAN: slab-use-after-free Read in wg_noise_keypair_get
Date: Tue, 18 Jul 2023 16:02:53 -0500	[thread overview]
Message-ID: <97a9c205-2074-07f8-ae9d-9f2b4aebbf9a@oracle.com> (raw)
In-Reply-To: <CAHmME9reBny-ufJp58uOg+KdMptircBRhLFd-N2KwxNUp6myTA@mail.gmail.com>

On 7/18/23 12:57PM, Jason A. Donenfeld wrote:
> Freed in:
> 
>   diUnmount+0xf3/0x100 fs/jfs/jfs_imap.c:195
>   jfs_umount+0x186/0x3a0 fs/jfs/jfs_umount.c:63
>   jfs_put_super+0x8a/0x190 fs/jfs/super.c:194
> 
> So maybe not a wg issue?

Maybe not. It could possibly fixed by:
https://github.com/kleikamp/linux-shaggy/commit/6e2bda2c192d0244b5a78b787ef20aa10cb319b7

Shaggy

  reply	other threads:[~2023-07-19 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 15:21 syzbot
2023-07-18 17:57 ` Jason A. Donenfeld
2023-07-18 21:02   ` Dave Kleikamp [this message]
2023-07-19 15:02     ` [Jfs-discussion] " Christian Kujau
2023-07-19 17:52       ` 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=97a9c205-2074-07f8-ae9d-9f2b4aebbf9a@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=Jason@zx2c4.com \
    --cc=broonie@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=kuba@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=povik+lin@cutebit.org \
    --cc=syzbot+96eb4e0d727f0ae998a6@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).