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
| ||
|
Message-ID: <20121206184204.GE2862@kroah.com> Date: Thu, 6 Dec 2012 10:42:04 -0800 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: Herton Ronaldo Krzesinski <herton.krzesinski@...onical.com> Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org, alan@...rguk.ukuu.org.uk, Yang Wei <wei.yang@...driver.com>, Robert Richter <robert.richter@....com>, "H. Peter Anvin" <hpa@...ux.intel.com>, Jun Zhang <jun.zhang@...el.com> Subject: Re: [ 09/56] x86-32: Fix invalid stack address while in softirq On Tue, Dec 04, 2012 at 11:56:46AM -0200, Herton Ronaldo Krzesinski wrote: > On Fri, Nov 30, 2012 at 10:55:01AM -0800, Greg Kroah-Hartman wrote: > > 3.4-stable review patch. If anyone has any objections, please let me know. > > > > ------------------ > > > > From: Robert Richter <robert.richter@....com> > > > > commit 1022623842cb72ee4d0dbf02f6937f38c92c3f41 upstream. > > > > In 32 bit the stack address provided by kernel_stack_pointer() may > > point to an invalid range causing NULL pointer access or page faults > > while in NMI (see trace below). This happens if called in softirq > > context and if the stack is empty. The address at ®s->sp is then > > out of range. > > > > Fixing this by checking if regs and ®s->sp are in the same stack > > context. Otherwise return the previous stack pointer stored in struct > > thread_info. If that address is invalid too, return address of regs. > > > > This also makes latest 3.4.y build fail with oprofile on i386, needs > also EXPORT_SYMBOL for kernel_stack_pointer (commit > cb57a2b4cff7edf2a4e32c0163200e9434807e0a) Sorry, now fixed with 3.4.22 -- 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/
Powered by blists - more mailing lists