From: Eric Biggers <ebiggers@kernel.org>
To: Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
kasan-dev@googlegroups.com
Cc: Dmitry Vyukov <dvyukov@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] kmsan: Fix out-of-bounds access to shadow memory
Date: Wed, 10 Sep 2025 19:49:21 +0000 [thread overview]
Message-ID: <20250910194921.GA3153735@google.com> (raw)
In-Reply-To: <20250829164500.324329-1-ebiggers@kernel.org>
On Fri, Aug 29, 2025 at 09:45:00AM -0700, Eric Biggers wrote:
> Running sha224_kunit on a KMSAN-enabled kernel results in a crash in
> kmsan_internal_set_shadow_origin():
>
> BUG: unable to handle page fault for address: ffffbc3840291000
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> PGD 1810067 P4D 1810067 PUD 192d067 PMD 3c17067 PTE 0
> Oops: 0000 [#1] SMP NOPTI
> CPU: 0 UID: 0 PID: 81 Comm: kunit_try_catch Tainted: G N 6.17.0-rc3 #10 PREEMPT(voluntary)
> Tainted: [N]=TEST
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014
> RIP: 0010:kmsan_internal_set_shadow_origin+0x91/0x100
> [...]
> Call Trace:
> <TASK>
> __msan_memset+0xee/0x1a0
> sha224_final+0x9e/0x350
> test_hash_buffer_overruns+0x46f/0x5f0
> ? kmsan_get_shadow_origin_ptr+0x46/0xa0
> ? __pfx_test_hash_buffer_overruns+0x10/0x10
> kunit_try_run_case+0x198/0xa00
Any thoughts on this patch from the KMSAN folks? I'd love to add
CONFIG_KMSAN=y to my crypto subsystem testing, but unfortunately the
kernel crashes due to this bug :-(
- Eric
next prev parent reply other threads:[~2025-09-10 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 16:45 Eric Biggers
2025-09-10 19:49 ` Eric Biggers [this message]
2025-09-11 9:09 ` Alexander Potapenko
2025-09-11 17:51 ` Eric Biggers
2025-09-11 19:03 ` Eric Biggers
2025-09-11 19:29 ` Eric Biggers
2025-09-17 8:31 ` Alexander Potapenko
2025-09-17 15:48 ` Eric Biggers
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=20250910194921.GA3153735@google.com \
--to=ebiggers@kernel.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox