| 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
| ||
|
Date: Tue, 25 Nov 2014 11:19:36 -0800 From: Kees Cook <keescook@...omium.org> To: Fengguang Wu <fengguang.wu@...el.com> Cc: "Qian, Shijun" <shijun.qian@...el.com>, "Bernal Marin, Miguel" <miguel.bernal.marin@...el.com>, Yuanhan Liu <yuanhan.liu@...el.com>, LKML <linux-kernel@...r.kernel.org>, "# 3.4.x" <stable@...r.kernel.org> Subject: Re: [stable] KASLR could not find suitable E820 region... On Tue, Nov 25, 2014 at 11:14 AM, Fengguang Wu <fengguang.wu@...el.com> wrote: > Hi Kees, > > We noticed the below boot errors in stable kernels 3.16.7 and 3.17.2 > on real hardwares: > > early console in decompress_kernel > KASLR could not find suitable E820 region... > > Decompressing Linux... Parsing ELF... Performing relocations... > > 32-bit relocation outside of kernel! > > These kconfig options are enabled: > > CONFIG_RANDOMIZE_BASE=y > CONFIG_RANDOMIZE_BASE_MAX_OFFSET=0x40000000 > > Before digging further, we'd like to ask for a quick answer that > whether they've been fixed by some commit in current mainline kernel? Possibly. There are recent fixes to the bss/brk detection code, which could lead to corruptions. Normally they've all be initramfs corruption, so relocation corruption seems unlikely. If these boots are due to loading kernels above 4G, there are still patches being discussed to solve those problems. -Kees -- Kees Cook Chrome OS Security -- 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