public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "weizhenvul at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/26577] Stack overflow in dlopen
Date: Mon, 07 Sep 2020 10:12:09 +0000	[thread overview]
Message-ID: <bug-26577-131-rr9VSL155k@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26577-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26577

--- Comment #2 from SunshineFly <weizhenvul at gmail dot com> ---
(In reply to Florian Weimer from comment #1)
> This is caused by the alloca in dl-load.c during pathname construction. We
> cannot trivially replace this with malloc because this allocation would leak
> most of the time because of the way free works for the dl-minimal.c malloc.
> 
> I'm setting security- (no security impact) because the dlopen argument does
> not cross a trust boundary.
> 
> -- 
> Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
> Commercial register: Amtsgericht Muenchen, HRB 153243,
> Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael
> O'Neill

I analyzed the availability of the problem and concluded that it would only
cause a crash.
I think it's a safety issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-09-07 10:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07  7:17 [Bug libc/26577] New: Stack overflow in dlope weizhenvul at gmail dot com
2020-09-07  7:18 ` [Bug libc/26577] Stack overflow in dlopen weizhenvul at gmail dot com
2020-09-07  9:30 ` [Bug dynamic-link/26577] " fweimer at redhat dot com
2020-09-07 10:12 ` weizhenvul at gmail dot com [this message]
2020-09-07 17:08 ` joseph at codesourcery dot com

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=bug-26577-131-rr9VSL155k@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).