[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrWZ=sipwoVic16LM08+-FKV5knO7Cv3pSM_5w=KLCqTKw@mail.gmail.com>
Date: Mon, 25 Jun 2018 08:47:40 -0700
From: Andy Lutomirski <luto@...nel.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Andrew Lutomirski <luto@...nel.org>,
Borislav Petkov <bp@...en8.de>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Greg KH <gregkh@...uxfoundation.org>, rafael.tinoco@...aro.org,
Shuah Khan <shuah@...nel.org>, Ingo Molnar <mingo@...nel.org>
Subject: Re: qemu-system-x86_64: mov_ss_trap_64 PANIC: double fault,
error_code: 0x0
On Sun, Jun 24, 2018 at 10:41 PM Naresh Kamboju
<naresh.kamboju@...aro.org> wrote:
>
> Kselftest test case mov_ss_trap_64 is causing kernel panic on
> qemu-system-x86_64 and PASS on real x86_64 hardware.
>
> Test code snippet,
> main() {
> <>
> printf("[RUN]\tMOV SS; CS CS INT3\n");
> asm volatile ("mov %[ss], %%ss; .byte 0x2e, 0x2e; int3" :: [ss] "m" (ss));
> <>
> }
>
This smells like CVE-2018-1087. Can you confirm that your *host*
kernel is patched?
CVE-2018-1087 is extremely severe, and if your host kernel is not
patched, I think you need to apply some serious pressure on your
vendor to get with the program.
--Andy
Powered by blists - more mailing lists