public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/28340] New: ld.so crashes while loading a DSO with a read-only dynamic section
Date: Tue, 14 Sep 2021 17:46:42 +0000 [thread overview]
Message-ID: <bug-28340-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28340
Bug ID: 28340
Summary: ld.so crashes while loading a DSO with a read-only
dynamic section
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: dynamic-link
Assignee: siddhesh at sourceware dot org
Reporter: siddhesh at sourceware dot org
Target Milestone: ---
ld.so crashes when trying to verify DSO with read-only dynamic section, e.g.
vdso64.so as shipped by the Linux kernel.
$ elf/ld.so --verify $(find /usr -name vdso64.so | head -1)
Actual Result:
Segfault
Expected Result:
Not crash
Since there's no way to load a dynamic object that has a read-only .dynamic
section and at the same time, has entries in the .dynamic section that need
adjustment during relocation, e.g. .plt.got address, .symtab address, etc.,
fail to load and return an error.
Patch coming up.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-09-14 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 17:46 siddhesh at sourceware dot org [this message]
2021-09-14 17:46 ` [Bug dynamic-link/28340] " siddhesh at sourceware dot org
2021-09-22 18:14 ` cvs-commit at gcc dot gnu.org
2021-09-22 18:27 ` hjl.tools at gmail dot com
2021-09-24 16:27 ` fweimer at redhat dot com
2021-09-25 16:29 ` cvs-commit at gcc dot gnu.org
2021-10-19 13:41 ` cvs-commit at gcc dot gnu.org
2021-11-03 9:59 ` cvs-commit at gcc dot gnu.org
2021-11-03 9:59 ` cvs-commit at gcc dot gnu.org
2021-11-03 9:59 ` cvs-commit at gcc dot gnu.org
2021-11-05 0:39 ` sam at gentoo dot org
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-28340-131@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).