linux-kernel - Re: [RFC PATCH] binfmt_elf: Fix PIE execution with randomization disabled

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]

Date:	Mon, 3 Oct 2011 16:53:34 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Josh Boyer <jwboyer@...hat.com>
Cc:	Nicolas Pitre <nicolas.pitre@...aro.org>,
	Andrew Morton <akpm00@...il.com>, Ingo Molnar <mingo@...e.hu>,
	hongjiu.lu@...el.com, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Russell King <rmk@....linux.org.uk>
Subject: Re: [RFC PATCH] binfmt_elf: Fix PIE execution with randomization
 disabled

On Thu, 29 Sep 2011, Josh Boyer wrote:

> Perhaps another check here for randomize?  Something like:
> 
> #if defined(CONFIG_X86) || defined(CONFIG_ARM)
> 		if (current->flags & PF_RANDOMIZE)
> 			load_bias = 0;
> 		else if (vaddr)
> 			load_bias = 0;
> 		else
> 			load_bias = ELF_PAGESTART(ELF_ET_DYN_BASE);
> #else
> 		load_bias = ELF_PAGESTART(ELF_ET_DYN_BASE - vaddr);
> #endif
> 
> If that's stupid, then feel free to tell me.  I won't pretend like I
> understand what is going on here yet, but based on the explanation you
> provided that might work.

I have just verified my hunch that the original patch from H.J. / Josh 
breaks ASLR completely, so Andrew, please drop it for now.

I am now looking into how to fix things properly.

Josh, looking at what you are proposing -- do you see any reason to make 
the behavior different in #else branch and in !(current->flags & 
PF_RANDOMIZE) case?

-- 
Jiri Kosina
SUSE Labs
--
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/