From: Richard Kojedzinszky <richard@kojedz.in>
To: Kees Cook <keescook@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Ali Saidi <alisaidi@amazon.com>,
Guenter Roeck <linux@roeck-us.net>,
Michal Hocko <mhocko@suse.com>,
Matthew Wilcox <willy@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jann Horn <jannh@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] binfmt_elf: Do not move brk for INTERP-less ET_EXEC
Date: Fri, 27 Sep 2019 08:16:53 +0200 [thread overview]
Message-ID: <321faad3c5e1f8eaf9d81fd78f3b22d6@kojedz.in> (raw)
In-Reply-To: <201909261136.780526BB@keescook>
Hi,
Thanks for the fix, again. I am not familiar with the code here, I
suspect the intent was to fix or improve something. That happens
sometimes, that things get broken. I am happy that I could report it,
and it got fixed quickly.
Thanks again,
Richard
2019-09-26 20:37 időpontban Kees Cook ezt írta:
> On Thu, Sep 26, 2019 at 08:26:12PM +0200, Richard Kojedzinszky wrote:
>> Thanks for the quick patch. It seems my binaries start up well, and
>> work as
>> expected, as before.
>>
>> Thanks again for the quick response.
>
> Awesome; thanks for the testing (and sorry for the breakage)! :)
>
> -Kees
>
>>
>> Regards,
>> Richard Kojedzinszky
>>
>> 2019-09-26 19:15 időpontban Kees Cook ezt írta:
>> > When brk was moved for binaries without an interpreter, it should have
>> > been limited to ET_DYN only. In other words, the special case was an
>> > ET_DYN that lacks an INTERP, not just an executable that lacks INTERP.
>> > The bug manifested for giant static executables, where the brk would end
>> > up in the middle of the text area on 32-bit architectures.
>> >
>> > Reported-by: Richard Kojedzinszky <richard@kojedz.in>
>> > Fixes: bbdc6076d2e5 ("binfmt_elf: move brk out of mmap when doing
>> > direct loader exec")
>> > Cc: stable@vger.kernel.org
>> > Signed-off-by: Kees Cook <keescook@chromium.org>
>> > ---
>> > Richard, are you able to test this? I'm able to run the gitea binary
>> > with this change, and my INTERP-less ET_DYN tests (from the original
>> > bug) continue to pass as well.
>> > ---
>> > fs/binfmt_elf.c | 3 ++-
>> > 1 file changed, 2 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c
>> > index cec3b4146440..ad4c6b1d5074 100644
>> > --- a/fs/binfmt_elf.c
>> > +++ b/fs/binfmt_elf.c
>> > @@ -1121,7 +1121,8 @@ static int load_elf_binary(struct linux_binprm
>> > *bprm)
>> > * (since it grows up, and may collide early with the stack
>> > * growing down), and into the unused ELF_ET_DYN_BASE region.
>> > */
>> > - if (IS_ENABLED(CONFIG_ARCH_HAS_ELF_RANDOMIZE) && !interpreter)
>> > + if (IS_ENABLED(CONFIG_ARCH_HAS_ELF_RANDOMIZE) &&
>> > + loc->elf_ex.e_type == ET_DYN && !interpreter)
>> > current->mm->brk = current->mm->start_brk =
>> > ELF_ET_DYN_BASE;
>> >
>> > --
>> > 2.17.1
prev parent reply other threads:[~2019-09-27 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 17:15 Kees Cook
2019-09-26 18:26 ` Richard Kojedzinszky
2019-09-26 18:37 ` Kees Cook
2019-09-27 6:16 ` Richard Kojedzinszky [this message]
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=321faad3c5e1f8eaf9d81fd78f3b22d6@kojedz.in \
--to=richard@kojedz.in \
--cc=akpm@linux-foundation.org \
--cc=alisaidi@amazon.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mhocko@suse.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
/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
all inboxes | Powered by JetHome®