From: Guinevere Larsen <guinevere@redhat.com>
To: gdb-patches@sourceware.org
Cc: Guinevere Larsen <guinevere@redhat.com>, Simon Marchi <simark@simark.ca>
Subject: [PATCH] gdb: Fix use-after-free when an objfile has no symbols to load
Date: Thu, 5 Dec 2024 10:19:59 -0300 [thread overview]
Message-ID: <20241205131959.3400690-1-guinevere@redhat.com> (raw)
The recent commit <HASH> moved an initialization of an objfile_holder in
syms_from_objfile_1 much earlier in the function, to better deal with
when GDB is unable to read the objfile format.
However, there is an early exit from syms_from_objfile_1 when the
objfile can be understood, but has no symbols. That was not releasing
the objfile_holder, so the objfile was being unlinked from the program
space, but the process of reading the objfile was being continued,
leading to use-after-frees flagged by the Address Sanitizer.
This commit fixes that UAF by making the objfile_holder release the
objfile right before the early exit.
This commit also changes the test gdb.base/dump.exp since that was the
original test that flagged the UAF, but at the end of the test the
generated files were being deleted, meaning we couldn't redo the test
manually after teh fact. That final deletion was removed
Reported-by: Simon Marchi <simark@simark.ca>
---
gdb/symfile.c | 4 ++++
gdb/testsuite/gdb.base/dump.exp | 4 ----
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/gdb/symfile.c b/gdb/symfile.c
index 3fd6c8d73a2..28c0d46ab54 100644
--- a/gdb/symfile.c
+++ b/gdb/symfile.c
@@ -901,6 +901,10 @@ syms_from_objfile_1 (struct objfile *objfile,
int num_sections = gdb_bfd_count_sections (objfile->obfd.get ());
objfile->section_offsets.assign (num_sections, 0);
+
+ /* Release the objfile unique pointer, since nothing went wrong
+ in reading it. */
+ objfile_holder.release ();
return;
}
diff --git a/gdb/testsuite/gdb.base/dump.exp b/gdb/testsuite/gdb.base/dump.exp
index 3c7bee5ff30..58fedb1d36b 100644
--- a/gdb/testsuite/gdb.base/dump.exp
+++ b/gdb/testsuite/gdb.base/dump.exp
@@ -564,7 +564,3 @@ if {![string compare $is64bitonly "no"]} {
"reload struct as memory, tekhex" \
$struct_val "\*$struct_ptr_type"
}
-
-# clean up files
-
-remote_exec host "rm -f $filenames"
--
2.47.0
next reply other threads:[~2024-12-05 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 13:19 Guinevere Larsen [this message]
2024-12-05 13:54 ` Guinevere Larsen
2024-12-06 17:35 ` Simon Marchi
2024-12-06 17:37 ` Guinevere Larsen
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=20241205131959.3400690-1-guinevere@redhat.com \
--to=guinevere@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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