From: "Geyslan G. Bem" <geyslan@gmail.com>
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-br@googlegroups.com, "Geyslan G. Bem" <geyslan@gmail.com>
Subject: [PATCH v2] fs: binfmt_elf: Add ELF header consistency checks
Date: Wed, 20 Nov 2013 21:34:31 -0300 [thread overview]
Message-ID: <1384994071-12283-1-git-send-email-geyslan@gmail.com> (raw)
The member 'e_ehsize' that holds the ELF header size is compared
with the elfhdr struct size. If not equal, goes out.
If 'e_phoff' holds 0 the object has no program header table, so
goes out.
Ensures the file being loaded has the correct data encoding, checking
'e_ident[EI_DATA]' against 'ELF_DATA'.
Besides the checks being in accordance with the ELF Specifications,
they increase the binary consistency reducing the use of malformed ones.
Signed-off-by: Geyslan G. Bem <geyslan@gmail.com>
---
fs/binfmt_elf.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c
index 571a423..326ca39 100644
--- a/fs/binfmt_elf.c
+++ b/fs/binfmt_elf.c
@@ -603,14 +603,20 @@ static int load_elf_binary(struct linux_binprm *bprm)
if (memcmp(loc->elf_ex.e_ident, ELFMAG, SELFMAG) != 0)
goto out;
+ if (loc->elf_ex.e_ehsize != sizeof(struct elfhdr))
+ goto out;
if (loc->elf_ex.e_type != ET_EXEC && loc->elf_ex.e_type != ET_DYN)
goto out;
if (!elf_check_arch(&loc->elf_ex))
goto out;
+ if (loc->elf_ex.e_ident[EI_DATA] != ELF_DATA)
+ goto out;
if (!bprm->file->f_op->mmap)
goto out;
/* Now read in all of the header information */
+ if (loc->elf_ex.e_phoff == 0)
+ goto out;
if (loc->elf_ex.e_phentsize != sizeof(struct elf_phdr))
goto out;
if (loc->elf_ex.e_phnum < 1 ||
--
1.8.4.2
next reply other threads:[~2013-11-21 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 0:34 Geyslan G. Bem [this message]
2013-11-21 1:39 ` [PATCH v2] fs: binfmt_elf: Add ELF header consistency checks Al Viro
2013-11-21 10:52 ` Geyslan Gregório Bem
2013-11-22 9:45 ` Geyslan Gregório Bem
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1384994071-12283-1-git-send-email-geyslan@gmail.com \
--to=geyslan@gmail.com \
--cc=kernel-br@googlegroups.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).