linux-kernel - Re: Oops with tip/x86/fpu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150327073020.GB6295@chrystal.uk.oracle.com>
Date:	Fri, 27 Mar 2015 08:30:20 +0100
From:	Quentin Casasnovas <quentin.casasnovas@...cle.com>
To:	"Yu, Fenghua" <fenghua.yu@...el.com>
Cc:	"Hansen, Dave" <dave.hansen@...el.com>,
	Oleg Nesterov <oleg@...hat.com>, Borislav Petkov <bp@...e.de>,
	Quentin Casasnovas <quentin.casasnovas@...cle.com>,
	Andy Lutomirski <luto@...capital.net>,
	Ingo Molnar <mingo@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Pekka Riikonen <priikone@....fi>,
	Rik van Riel <riel@...hat.com>,
	Suresh Siddha <sbsiddha@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Oops with tip/x86/fpu

On Thu, Mar 26, 2015 at 10:48:18PM +0000, Yu, Fenghua wrote:
> > > sctxt->fpstate=(void *)1 changes the fpstate pointer in the
> > > sigcontext. It will generate segfault and bad frame info in kernel.
> > >
> > > This is expected behavior, right? Is this still a valid test?
> > 
> > Just to be clear, I saw a full-on kernel panic induced from an unprivileged
> > application.
> > 
> > Are you seeing something different?
> 
> I use latest tip tree. Maybe it has the fixes already. I see "bad frame"
> reported in kernel. Seems the issue has been fixed in tip tree.
> 

Fenghua, if you're interested, the details are now public here:

 http://seclists.org/oss-sec/2015/q1/877

Quentin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/