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, 9 Dec 2013 13:03:37 -0800
From:	"H.J. Lu" <hjl.tools@...il.com>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Josh Boyer <jwboyer@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] binfmt_elf: fix PIE load with randomization disabled

On Mon, Dec 9, 2013 at 12:57 PM, Jiri Kosina <jkosina@...e.cz> wrote:
> On Mon, 9 Dec 2013, H.J. Lu wrote:
>
>> Normally, a PIE executable has zero virtual address on the first PT_LOAD
>> segment and kernel will load such executable at random address when
>> randomization is enabled.  If randomization is disabled, kernel will load
>> it at a fixed address.  But if a PIE executable has non-zero virtual
>> address on the first PT_LOAD segment, kernel will load such executable
>> at the non-zero virtual address when randomization is enabled. But when
>> randomization is disabled, kernel ignores the non-zero virtual address
>> at the non-zero virtual address when randomization is enabled.
>
> Hmm ... isn't actually this the thing that needs to be fixed instead?
>
> IOW, when randomization is enabled, is there a reason not to load on
> randomized address? (even if the first PT_LOAD segment has non-zero
> vaddr?)

No, please don't do that.  Normally, PIE has zero load address and kernel
can load it anywhere.  There are multiple reasons why PIE has non-zero
load address.  Saying you need to load a program above 4GB under x86-64,
you can't do that with normal dynamic executable.  PIE with non-zero load
address is the only way to do that on x86-64.

>> But when randomization is disabled, kernel ignores the non-zero virtual
>> address on the first PT_LOAD segment and loads it at the fixed address.
>> This patch makes kernel consistent by loading PIE executable with
>> non-zero virtual address at the non-zero virtual address, regardless if
>> randomization is enabled or disabled.
>


-- 
H.J.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ