From: Eric Biggers <ebiggers@kernel.org>
To: syzbot <syzbot+14c6a89d5f47cd26ea7a@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?] general protection fault in xxh64_update
Date: Mon, 8 Sep 2025 18:47:19 +0000 [thread overview]
Message-ID: <20250908184719.GB189309@google.com> (raw)
In-Reply-To: <68bebd63.050a0220.192772.086e.GAE@google.com>
On Mon, Sep 08, 2025 at 04:26: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=12951312580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=fbc16d9faf3a88a4
> dashboard link: https://syzkaller.appspot.com/bug?extid=14c6a89d5f47cd26ea7a
> 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=16951312580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10b8e962580000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/36645a51612c/disk-4ac65880.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/bba80d634bef/vmlinux-4ac65880.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/e58dd70dfd0f/bzImage-4ac65880.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+14c6a89d5f47cd26ea7a@syzkaller.appspotmail.com
>
> Oops: general protection fault, probably for non-canonical address 0xe0009d1000000000: 0000 [#1] SMP KASAN PTI
> KASAN: maybe wild-memory-access in range [0x0005088000000000-0x0005088000000007]
> CPU: 0 UID: 0 PID: 6069 Comm: syz.0.32 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
> RIP: 0010:get_unaligned_le64 include/linux/unaligned.h:28 [inline]
> RIP: 0010:xxh64_update+0x55b/0xcf0 lib/xxhash.c:312
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:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 11:26 [syzbot] [crypto?] general protection fault in xxh64_update syzbot
2025-09-08 18:47 ` 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=20250908184719.GB189309@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+14c6a89d5f47cd26ea7a@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