From: Eric Biggers <ebiggers@kernel.org>
To: syzbot <syzbot+e37eedd918576774ec80@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [crypto?] KASAN: wild-memory-access Read in __sha512_update
Date: Mon, 8 Sep 2025 18:46:53 +0000 [thread overview]
Message-ID: <20250908184653.GA189309@google.com> (raw)
In-Reply-To: <68beb07f.050a0220.192772.086a.GAE@google.com>
On Mon, Sep 08, 2025 at 03:31:27AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 4ac65880ebca Add linux-next specific files for 20250904
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=11136312580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=1220fefb3f11f346
> dashboard link: https://syzkaller.appspot.com/bug?extid=e37eedd918576774ec80
> 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=15136312580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16e23e62580000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/17aafe2d8f53/disk-4ac65880.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/09caead80fb0/vmlinux-4ac65880.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/b33c041f8dc2/bzImage-4ac65880.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+e37eedd918576774ec80@syzkaller.appspotmail.com
>
> ==================================================================
> BUG: KASAN: wild-memory-access in __sha512_update+0x10d/0x1d0 lib/crypto/sha512.c:175
> Read of size 2 at addr 0005088000000000 by task syz.0.17/6022
Bug in mm/gup.c that reached linux-next but has already been fixed.
#syz dup: KASAN: null-ptr-deref Read in io_sqe_buffer_register
- Eric
prev parent reply other threads:[~2025-09-08 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 10:31 [syzbot] [crypto?] KASAN: wild-memory-access Read in __sha512_update syzbot
2025-09-08 12:02 ` Edward Adam Davis
2025-09-08 12:55 ` syzbot
2025-09-08 18:46 ` Eric Biggers [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=20250908184653.GA189309@google.com \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+e37eedd918576774ec80@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 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.