aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/binutils/binutils
diff options
context:
space:
mode:
authorFan Xin <fan.xin@jp.fujitsu.com>2017-05-24 14:43:11 +0900
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-05-25 23:57:01 +0100
commitdff01b827c87ae135a1d5511b1efbdad01c0eaee (patch)
tree35904f229353bb5180b9eb89e580eff7fb7cad47 /meta/recipes-devtools/binutils/binutils
parent0492eb8d781c49e29139d42973832593dd69cae5 (diff)
downloadopenembedded-core-contrib-dff01b827c87ae135a1d5511b1efbdad01c0eaee.tar.gz
binutils: Fix CVE-2017-8392
Backport upsream commit to fix CVE-2017-8392 CVE: CVE-2017-8392 [BZ 21409] -- https://sourceware.org/bugzilla/show_bug.cgi?id=21409 PR 21409, segfault in _bfd_dwarf2_find_nearest_line PR 21409 * dwarf2.c (_bfd_dwarf2_find_nearest_line): Don't segfault when no symbols. Signed-off-by: Fan Xin <fan.xin@jp.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/recipes-devtools/binutils/binutils')
-rw-r--r--meta/recipes-devtools/binutils/binutils/0017-bfd-Improve-lookup-of-file-line-information-for-erro.patch75
-rw-r--r--meta/recipes-devtools/binutils/binutils/0018-PR-21409-segfault-in-_bfd_dwarf2_find_nearest_line.patch33
2 files changed, 108 insertions, 0 deletions
diff --git a/meta/recipes-devtools/binutils/binutils/0017-bfd-Improve-lookup-of-file-line-information-for-erro.patch b/meta/recipes-devtools/binutils/binutils/0017-bfd-Improve-lookup-of-file-line-information-for-erro.patch
new file mode 100644
index 0000000000..23ad10ab4a
--- /dev/null
+++ b/meta/recipes-devtools/binutils/binutils/0017-bfd-Improve-lookup-of-file-line-information-for-erro.patch
@@ -0,0 +1,75 @@
+From 3239a4231ff79bf8b67b8faaf414b1667486167c Mon Sep 17 00:00:00 2001
+From: Andrew Burgess <andrew.burgess@embecosm.com>
+Date: Mon, 19 Dec 2016 15:27:59 +0000
+Subject: [PATCH] bfd: Improve lookup of file / line information for errors
+
+When looking up file and line information (used from the linker to
+report error messages) if no symbol is passed in, then use the symbol
+list to look for a matching symbol.
+
+If a matching symbol is found then use this to look up the file / line
+information.
+
+This should improve errors when looking up file / line information for
+data sections. Hopefully we should find a matching data symbol, which
+should, in turn (we hope) match a DW_TAG_variable in the DWARF, this
+should allow us to give accurate file / line errors for data symbols.
+
+As the hope is to find a matching DW_TAG_variable in the DWARF then we
+ignore section symbols, and prefer global symbols to locals.
+
+CVE: CVE-2017-8392
+Upstream-Status: Accepted
+
+Signed-off-by: Fan Xin <fan.xin@jp.fujitsu.com>
+---
+ bfd/dwarf2.c | 32 ++++++++++++++++++++++++++++++++
+ 1 files changed, 32 insertions(+)
+
+
+diff --git a/bfd/dwarf2.c b/bfd/dwarf2.c
+index 03447a9..9bb8126 100644
+--- a/bfd/dwarf2.c
++++ b/bfd/dwarf2.c
+@@ -4155,6 +4155,38 @@ _bfd_dwarf2_find_nearest_line (bfd *abfd,
+ {
+ BFD_ASSERT (section != NULL && functionname_ptr != NULL);
+ addr = offset;
++
++ /* If we have no SYMBOL but the section we're looking at is not a
++ code section, then take a look through the list of symbols to see
++ if we have a symbol at the address we're looking for. If we do
++ then use this to look up line information. This will allow us to
++ give file and line results for data symbols. We exclude code
++ symbols here, if we look up a function symbol and then look up the
++ line information we'll actually return the line number for the
++ opening '{' rather than the function definition line. This is
++ because looking up by symbol uses the line table, in which the
++ first line for a function is usually the opening '{', while
++ looking up the function by section + offset uses the
++ DW_AT_decl_line from the function DW_TAG_subprogram for the line,
++ which will be the line of the function name. */
++ if ((section->flags & SEC_CODE) == 0)
++ {
++ asymbol **tmp;
++
++ for (tmp = symbols; (*tmp) != NULL; ++tmp)
++ if ((*tmp)->the_bfd == abfd
++ && (*tmp)->section == section
++ && (*tmp)->value == offset
++ && ((*tmp)->flags & BSF_SECTION_SYM) == 0)
++ {
++ symbol = *tmp;
++ do_line = TRUE;
++ /* For local symbols, keep going in the hope we find a
++ global. */
++ if ((symbol->flags & BSF_GLOBAL) != 0)
++ break;
++ }
++ }
+ }
+
+ if (section->output_section)
+--
+1.9.1
+
diff --git a/meta/recipes-devtools/binutils/binutils/0018-PR-21409-segfault-in-_bfd_dwarf2_find_nearest_line.patch b/meta/recipes-devtools/binutils/binutils/0018-PR-21409-segfault-in-_bfd_dwarf2_find_nearest_line.patch
new file mode 100644
index 0000000000..acb37df168
--- /dev/null
+++ b/meta/recipes-devtools/binutils/binutils/0018-PR-21409-segfault-in-_bfd_dwarf2_find_nearest_line.patch
@@ -0,0 +1,33 @@
+From 97e83a100aa8250be783304bfe0429761c6e6b6b Mon Sep 17 00:00:00 2001
+From: Alan Modra <amodra@gmail.com>
+Date: Sun, 23 Apr 2017 13:55:49 +0930
+Subject: [PATCH] PR 21409, segfault in _bfd_dwarf2_find_nearest_line
+
+ PR 21409
+ * dwarf2.c (_bfd_dwarf2_find_nearest_line): Don't segfault when
+ no symbols.
+
+CVE: CVE-2017-8392
+Upstream-Status: Accepted
+
+Signed-off-by: Fan Xin <fan.xin@jp.fujitsu.com>
+---
+ bfd/dwarf2.c | 2 +-
+ 1 files changed, 1 insertions(+), 1 deletion(-)
+
+diff --git a/bfd/dwarf2.c b/bfd/dwarf2.c
+index 132a674..0ef3e1f 100644
+--- a/bfd/dwarf2.c
++++ b/bfd/dwarf2.c
+@@ -4205,7 +4205,7 @@ _bfd_dwarf2_find_nearest_line (bfd *abfd,
+ looking up the function by section + offset uses the
+ DW_AT_decl_line from the function DW_TAG_subprogram for the line,
+ which will be the line of the function name. */
+- if ((section->flags & SEC_CODE) == 0)
++ if (symbols != NULL && (section->flags & SEC_CODE) == 0)
+ {
+ asymbol **tmp;
+
+--
+1.9.1
+