All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d587b24799bd8c2d32f4@syzkaller.appspotmail.com>
To: bfoster@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	 davem@davemloft.net, herbert@gondor.apana.org.au, hpa@zytor.com,
	 kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
	 linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com,  mmpgouride@gmail.com,
	syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	 x86@kernel.org
Subject: Re: [syzbot] [bcachefs] KASAN: use-after-free Read in crypto_poly1305_update
Date: Thu, 17 Jul 2025 13:49:03 -0700	[thread overview]
Message-ID: <687961bf.a00a0220.3af5df.0023.GAE@google.com> (raw)
In-Reply-To: <67b2eaf8.050a0220.173698.0020.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit d89a34b14df5c205de698c23c3950b2b947cdb97
Author: Alan Huang <mmpgouride@gmail.com>
Date:   Sat Jun 14 09:18:07 2025 +0000

    bcachefs: Move bset size check before csum check

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1722a58c580000
start commit:   2408a807bfc3 Merge tag 'vfs-6.14-rc4.fixes' of git://git.k..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=6cc40dfe827ffb85
dashboard link: https://syzkaller.appspot.com/bug?extid=d587b24799bd8c2d32f4
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12c4f2e4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17e4c498580000

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

#syz fix: bcachefs: Move bset size check before csum check

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

  parent reply	other threads:[~2025-07-17 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17  7:53 [syzbot] [crypto?] KASAN: use-after-free Read in crypto_poly1305_update syzbot
2025-02-17 10:24 ` Ard Biesheuvel
2025-02-18 22:05 ` [syzbot] [bcachefs] " syzbot
2025-07-17 20:49 ` syzbot [this message]
2025-07-17 21:45 ` Forwarded: " 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=687961bf.a00a0220.3af5df.0023.GAE@google.com \
    --to=syzbot+d587b24799bd8c2d32f4@syzkaller.appspotmail.com \
    --cc=bfoster@redhat.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=hpa@zytor.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mmpgouride@gmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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.