From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tip-commits@vger.kernel.org,
Andy Lutomirski <luto@kernel.org>,
Brian Gerst <brgerst@gmail.com>,
"Chang S. Bae" <chang.seok.bae@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
x86@kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: hardened_usercopy 32-bit (was: Re: [tip: x86/merge] x86/fpu: Make task_struct::thread constant size)
Date: Sun, 4 May 2025 10:44:20 +0200 [thread overview]
Message-ID: <aBco5IostuyCepaT@gmail.com> (raw)
In-Reply-To: <aBcM7UXj8HQWZeHJ@gmail.com>
* Ingo Molnar <mingo@kernel.org> wrote:
>
> * Borislav Petkov <bp@alien8.de> wrote:
>
> > On Mon, Apr 14, 2025 at 07:34:48AM -0000, tip-bot2 for Ingo Molnar wrote:
> >
> > > The fpu_thread_struct_whitelist() quirk to hardened usercopy can be
> > > removed, now that the FPU structure is not embedded in the task
> > > struct anymore, which reduces text footprint a bit.
> >
> > Well, hardened usercopy still doesn't like it on 32-bit, see splat below:
> >
> > I did some debugging printks and here's what I see:
> >
> > That's the loop in copy_uabi_to_xstate(), copying the first FPU state
> > - XFEATURE_FP - to the kernel buffer:
> >
> > [ 1.752756] copy_uabi_to_xstate: i: 0 dst: 0xcab11f40, offset: 0, size: 160, kbuf: 0x00000000, ubuf: 0xbfcbca80
> > [ 1.754600] copy_from_buffer: dst: 0xcab11f40, src: 0xbfcbca80, size: 160
> >
> > hardened wants to check it:
> >
> > [ 1.755823] __check_heap_object: ptr: 0xcab11f40, slap_address: 0xcab10000, size: 2944
> > [ 1.757102] __check_heap_object: offset: 2112
> >
> > and figures out it is in some weird offset 2112 from *task_struct* even
> > though:
> >
> > [ 1.750149] copy_uabi_to_xstate: sizeof(task_struct): 1984
> >
> > btw, the buffer is big enough too:
> >
> > [ 1.749077] copy_uabi_to_xstate: sizeof(&fpstate->regs.xsave): 576
> >
> > but then it decides to BUG because an overwrite attempt is being done on
> > task_struct which is bollocks now as struct fpu is not part of it anymore.
> >
> > And this is where I'm all out of ideas so lemme CC folks.
>
> Thx for the report, mind sending the exact .config that fails for you?
BTW., mind sending the full bootlog as well? I cannot reproduce it here
with CONFIG_HARDENED_USERCOPY=y, so I suspect it's something about the
build, HW or boot environment.
Thanks,
Ingo
next prev parent reply other threads:[~2025-05-04 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 12:07 hardened_usercopy 32-bit (was: Re: [tip: x86/merge] x86/fpu: Make task_struct::thread constant size) Borislav Petkov
2025-05-04 6:45 ` Ingo Molnar
2025-05-04 8:44 ` Ingo Molnar [this message]
2025-05-04 9:50 ` Borislav Petkov
2025-05-04 9:53 ` Ingo Molnar
2025-05-04 22:30 ` Kees Cook
2025-05-04 22:43 ` Kees Cook
2025-05-05 9:15 ` Borislav Petkov
2025-05-05 11:31 ` Ingo Molnar
2025-05-05 21:09 ` Kees Cook
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=aBco5IostuyCepaT@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=chang.seok.bae@intel.com \
--cc=gustavoars@kernel.org \
--cc=hpa@zytor.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox