From: David Hildenbrand <david@redhat.com>
To: syzbot <syzbot+634e67b3f57206befe3c@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, davem@davemloft.net,
herbert@gondor.apana.org.au, jgg@ziepe.ca, jhubbard@nvidia.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, peterx@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [crypto?] KASAN: wild-memory-access Read in crypto_nhpoly1305_update_helper
Date: Wed, 10 Sep 2025 08:35:19 +0200 [thread overview]
Message-ID: <26a9495a-cee7-4db8-895c-aeb0f1784989@redhat.com> (raw)
In-Reply-To: <68c0f496.050a0220.3c6139.0017.GAE@google.com>
On 10.09.25 05:46, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: be5d4872e528 Add linux-next specific files for 20250905
^ old tag
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=10f70962580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a726684450a7d788
> dashboard link: https://syzkaller.appspot.com/bug?extid=634e67b3f57206befe3c
> compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1247a962580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12751134580000
>
#syz dup: [syzbot] [io-uring?] KASAN: null-ptr-deref Read in io_sqe_buffer_register
--
Cheers
David / dhildenb
prev parent reply other threads:[~2025-09-10 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 3:46 syzbot
2025-09-10 6:35 ` David Hildenbrand [this message]
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=26a9495a-cee7-4db8-895c-aeb0f1784989@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=syzbot+634e67b3f57206befe3c@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox