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-next>] [day] [month] [year] [list]
Message-ID: <sxokzxpo74u7yhrhfrmgtdvkpshwl464jicrwwkwtvkwl5d5dj@fqto77h2prj2>
Date: Fri, 27 Jun 2025 09:04:11 +0800
From: YinFengwei <fengwei_yin@...ux.alibaba.com>
To: linux-mm@...ck.org, linux-kernel@...r.kernel.org, 
	Kees Cook <kees@...nel.org>
Cc: fengwei_yin@...ux.alibaba.com, zhourundong.zrd@...ux.alibaba.com
Subject: [Question] About the elf program header size

Hi,
We had a script generated assembly code. built it with gcc and the
output elf file had 78 program headers.

On an arm64 platform, if we have 64KB base page size, the elf can
be started correctly. But if we have 4KB base page size, the elf
can NOT be started with:
    cannot execute binary file: Exec format error

Look at the function load_elf_phdrs():
        if (size == 0 || size > 65536 || size > ELF_MIN_ALIGN)
	                goto out;

ELF_MIN_ALIGN is defined as PAGE_SIZE on arm64. Which can explain
above inconsistent behaviors (from user perspetive).

I didn't find the limitation definition in ELF spec(Maybe I missed
some obvious info there). If I remove "size > ELF_MIN_ALIGN", the
same elf can be started correctly even with 4KB page size.

So my question is why we limit the who program headers total size
to PAGE_SIZE? git history couldn't tell anything because the
limitation was introduced when whole linux kernel tree was migrated
to git. Is there a possible constrain on other architecture? Thanks.


Regards
Yin, Fengwei


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ