From: Ingo Molnar <mingo@kernel.org>
To: kernel test robot <fengguang.wu@intel.com>
Cc: Eric Biggers <ebiggers@google.com>, LKP <lkp@01.org>,
linux-kernel@vger.kernel.org, Rik van Riel <riel@redhat.com>,
Kees Cook <keescook@chromium.org>,
wfg@linux.intel.com, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Date: Sun, 24 Sep 2017 12:00:53 +0200 [thread overview]
Message-ID: <20170924100053.26orenha4udgubtg@gmail.com> (raw)
In-Reply-To: <59c6e23f.nOk6ceVoId2JVMIx%fengguang.wu@intel.com>
* kernel test robot <fengguang.wu@intel.com> wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/fpu
>
> commit 9f4835fb965d8eea7e608d0cb62c246c804dec90
> Author: Eric Biggers <ebiggers@google.com>
> AuthorDate: Fri Sep 22 10:41:55 2017 -0700
> Commit: Ingo Molnar <mingo@kernel.org>
> CommitDate: Sat Sep 23 11:02:00 2017 +0200
>
> x86/fpu: Tighten validation of user-supplied xstate_header
So unfortunately the crash log was not extracted properly by the bot, so we only
know the subject line:
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
One possibility would be for this memcpy() in copy_kernel_to_xstate() to cause the
crash:
memcpy(&hdr, kbuf + offset, size);
where 'size' increased from:
size = sizeof(xfeatures);
which was 8 bytes, to:
size = sizeof(hdr);
which is 64 bytes.
What guarantees that 'kbuf + offset + size-1' is still within the kbuf buffer?
AFAICS 'kbuf' gets validated with fpu_user_xstate_size.
... I might be barking up the wrong tree, but I don't see this guaranteed, at
least not in any obvious way.
In hindsight, I think we need to split up this commit:
x86/fpu: Tighten validation of user-supplied xstate_header
Into at least 5-6 parts (!), as it's way too large and risky.
Here is the split-up I'd suggest:
1)
Introduce the new validate_xstate_header() function - without actually using it.
2)
Change xstateregs_set() to use validate_xstate_header() and change the behavior of
reserved bits. Since this impacts the ABI we better have this as a standalone,
bisectable patch.
3)
Change sanitize_restored_xstate() to use the new validate_xstate_header().
4)
Change copy_kernel_to_xstate() to introduce the new on-kernel-stack header copy,
but don't yet update the rest of the code, just initialize 'xfeatures' from the
header copy and leave the rest unchanged.
5)
Fix copy_kernel_to_xstate() to now use the header properly, pass it to
validate_xstate_header() and get rid of the 'xfeatures' local variable, etc.
6)
Also, while this change looks correct but it's unrelated and spurious:
- if (boot_cpu_has(X86_FEATURE_XSAVES)) {
+ if (using_compacted_format()) {
and using_compacted_format() is a stupidly global function that adds overhead
unnecessarily:
int using_compacted_format(void)
{
return boot_cpu_has(X86_FEATURE_XSAVES);
}
It should be a static inline instead.
Thanks,
Ingo
next prev parent reply other threads:[~2017-09-24 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 22:37 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b kernel test robot
2017-09-24 10:00 ` Ingo Molnar [this message]
2017-09-24 11:11 ` Ingo Molnar
2017-09-25 2:20 ` kernel test robot
2017-09-25 13:10 ` Fengguang Wu
2017-09-25 14:55 ` Ingo Molnar
2017-09-26 0:19 ` Fengguang Wu
2017-09-26 6:25 ` Ingo Molnar
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=20170924100053.26orenha4udgubtg@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=ebiggers@google.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=luto@kernel.org \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
--cc=wfg@linux.intel.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