From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Subject: asan: pef: buffer overflow
Date: Mon, 28 Nov 2022 20:15:10 +1030 [thread overview]
Message-ID: <Y4SDJrb7d7HMtR7H@squeak.grove.modra.org> (raw)
* pef.c (bfd_pef_parse_traceback_table): Correct size moved when
stripping leading dot.
diff --git a/bfd/pef.c b/bfd/pef.c
index 334d802eb75..e8672a40da7 100644
--- a/bfd/pef.c
+++ b/bfd/pef.c
@@ -181,7 +181,7 @@ bfd_pef_parse_traceback_table (bfd *abfd,
/* Strip leading period inserted by compiler. */
if (namebuf[0] == '.')
- memmove (namebuf, namebuf + 1, name.name_len + 1);
+ memmove (namebuf, namebuf + 1, name.name_len);
sym->name = namebuf;
--
Alan Modra
Australia Development Lab, IBM
reply other threads:[~2022-11-28 9:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Y4SDJrb7d7HMtR7H@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@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).