Summary
This update for binutils fixes the following issues:
- For compatibility on old code stream that expect 'brcl 0,label' to
not be disassembled as 'jgnop label' on s390x. (bsc#1192267)
This reverts IBM zSeries HLASM support for now.
- Fixed that ppc64 optflags did not enable LTO (bsc#1188941).
- Fix empty man-pages from broken release tarball
- Fixed a memory corruption with rpath option (bsc#1191473).
- Fixed slow performance of stripping some binaries (bsc#1183909).
Update to binutils 2.37:
* The GNU Binutils sources now requires a C99 compiler and library to
build.
* Support for Realm Management Extension (RME) for AArch64 has been
added.
* A new linker option '-z report-relative-reloc' for x86 ELF targets
has been added to report dynamic relative relocations.
* A new linker option '-z start-stop-gc' has been added to disable
special treatment of __start_*/__stop_* references when
--gc-sections.
* A new linker options '-Bno-symbolic' has been added which will
cancel the '-Bsymbolic' and '-Bsymbolic-functions' options.
* The readelf tool has a new command line option which can be used to
specify how the numeric values of symbols are reported.
--sym-base=0|8|10|16 tells readelf to display the values in base 8,
base 10 or base 16. A sym base of 0 represents the default action
of displaying values under 10000 in base 10 and values above that in
base 16.
* A new format has been added to the nm program. Specifying
'--format=just-symbols' (or just using -j) will tell the program to
only display symbol names and nothing else.
* A new command line option '--keep-section-symbols' has been added to
objcopy and strip. This stops the removal of unused section symbols
when the file is copied. Removing these symbols saves space, but
sometimes they are needed by other tools.
* The '--weaken', '--weaken-symbol' and '--weaken-symbols' options
supported by objcopy now make undefined symbols weak on targets that
support weak symbols.
* Readelf and objdump can now display and use the contents of .debug_sup
sections.
* Readelf and objdump will now follow links to separate debug info
files by default. This behaviour can be stopped via the use of the
new '-wN' or '--debug-dump=no-follow-links' options for readelf and
the '-WN' or '--dwarf=no-follow-links' options for objdump. Also
the old behaviour can be restored by the use of the
'--enable-follow-debug-links=no' configure time option.
The semantics of the =follow-links option have also been slightly
changed. When enabled, the option allows for the loading of symbol
tables and string tables from the separate files which can be used
to enhance the information displayed when dumping other sections,
but it does not automatically imply that information from the
separate files should be displayed.
If other debug section display options are also enabled (eg
'--debug-dump=info') then the contents of matching sections in both
the main file and the separate debuginfo file *will* be displayed.
This is because in most cases the debug section will only be present
in one of the files.
If however non-debug section display options are enabled (eg
'--sections') then the contents of matching parts of the separate
debuginfo file will *not* be displayed. This is because in most
cases the user probably only wanted to load the symbol information
from the separate debuginfo file. In order to change this behaviour
a new command line option --process-links can be used. This will
allow di0pslay options to applied to both the main file and any
separate debuginfo files.
* Nm has a new command line option: '--quiet'. This suppresses 'no
symbols' diagnostic.
Update to binutils 2.36:
New features in the Assembler:
- General:
* When setting the link order attribute of ELF sections, it is now
possible to use a numeric section index instead of symbol name.
* Added a .nop directive to generate a single no-op instruction in
a target neutral manner. This instruction does have an effect on
DWARF line number generation, if that is active.
* Removed --reduce-memory-overheads and --hash-size as gas now
uses hash tables that can be expand and shrink automatically.
- X86/x86_64:
* Add support for AVX VNNI, HRESET, UINTR, TDX, AMX and Key
Locker instructions.
* Support non-absolute segment values for lcall and ljmp.
* Add {disp16} pseudo prefix to x86 assembler.
* Configure with --enable-x86-used-note by default for Linux/x86.
- ARM/AArch64:
* Add support for Cortex-A78, Cortex-A78AE and Cortex-X1,
Cortex-R82, Neoverse V1, and Neoverse N2 cores.
* Add support for ETMv4 (Embedded Trace Macrocell), ETE (Embedded
Trace Extension), TRBE (Trace Buffer Extension), CSRE (Call
Stack Recorder Extension) and BRBE (Branch Record Buffer
Extension) system registers.
* Add support for Armv8-R and Armv8.7-A ISA extensions.
* Add support for DSB memory nXS barrier, WFET and WFIT
instruction for Armv8.7.
* Add support for +csre feature for -march. Add CSR PDEC
instruction for CSRE feature in AArch64.
* Add support for +flagm feature for -march in Armv8.4 AArch64.
* Add support for +ls64 feature for -march in Armv8.7
AArch64. Add atomic 64-byte load/store instructions for this
feature.
* Add support for +pauth (Pointer Authentication) feature for
-march in AArch64.
New features in the Linker:
* Add --error-handling-script=<NAME> command line option to allow
a helper script to be invoked when an undefined symbol or a
missing library is encountered. This option can be suppressed
via the configure time switch: --enable-error-handling-script=no.
* Add -z x86-64-{baseline|v[234]} to the x86 ELF linker to mark
x86-64-{baseline|v[234]} ISA level as needed.
* Add -z unique-symbol to avoid duplicated local symbol names.
* The creation of PE format DLLs now defaults
Fixed packages 4
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLE HPC 15 Linux Enterprise High Performance Computing 15-ESPOS | binutils | 2.37-6.23.1 |
| SUSE · SLE HPC 15 Linux Enterprise High Performance Computing 15-LTSS | binutils | 2.37-6.23.1 |
| SUSE · SLES 15 Linux Enterprise Server 15-LTSS | binutils | 2.37-6.23.1 |
| SUSE · SLES for SAP 15 Linux Enterprise Server for SAP Applications 15 | binutils | 2.37-6.23.1 |
Vulnerabilities 14
-
Medium 6.3
There is an open race window when writing output in the following utilities in GNU binutils version 2.35 and earlier:ar…
-
Unscored —
A double free vulnerability exists in the Binary File Descriptor (BFD) (aka libbrd) in GNU Binutils 2.35 in the process…
-
Unscored —
A Denial of Service vulnerability exists in the Binary File Descriptor (BFD) in GNU Binutils 2.35 due to an invalid rea…
-
Unscored —
A use after free issue exists in the Binary File Descriptor (BFD) library (aka libbfd) in GNU Binutils 2.34 in bfd_hash…
-
Unscored —
A Null Pointer Dereference vulnerability exists in the Binary File Descriptor (BFD) library (aka libbfd), as distribute…
-
Unscored —CVE-2020-16598 Rejected
DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigat…
-
Unscored —
A Null Pointer Dereference vulnerability exists in the Binary File Descriptor (BFD) library (aka libbfd), as distribute…
-
Unscored —
An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35.1…
-
Unscored —
A flaw exists in binutils in bfd/pef.c. An attacker who is able to submit a crafted PEF file to be parsed by objdump co…
-
Unscored —
There's a flaw in bfd_pef_scan_start_address() of bfd/pef.c in binutils which could allow an attacker who is able to su…
-
Unscored —
There's a flaw in bfd_pef_parse_function_stubs of bfd/pef.c in binutils in versions prior to 2.34 which could allow an …
-
Unscored —
A flaw was found in GNU Binutils 2.35.1, where there is a heap-based buffer overflow in _bfd_elf_slurp_secondary_reloc_…
-
Unscored —CVE-2021-20294 Public exploit
A flaw was found in binutils readelf 2.35 program. An attacker who is able to convince a victim using readelf to read a…
-
Unscored —CVE-2021-3487 Rejected
Non Security Issue. See the binutils security policy for more details, https://sourceware.org/cgit/binutils-gdb/tree/bi…
References
-
report
https://bugzilla.suse.com/1179898
-
report
https://bugzilla.suse.com/1179899
-
report
https://bugzilla.suse.com/1179900
-
report
https://bugzilla.suse.com/1179901
-
report
https://bugzilla.suse.com/1179902
-
report
https://bugzilla.suse.com/1179903
-
report
https://bugzilla.suse.com/1180451
-
report
https://bugzilla.suse.com/1180454
-
report
https://bugzilla.suse.com/1180461
-
report
https://bugzilla.suse.com/1181452
-
report
https://bugzilla.suse.com/1182252
-
report
https://bugzilla.suse.com/1183511
-
report
https://bugzilla.suse.com/1183909
-
report
https://bugzilla.suse.com/1184519
-
report
https://bugzilla.suse.com/1184620
-
report
https://bugzilla.suse.com/1184794
-
report
https://bugzilla.suse.com/1188941
-
report
https://bugzilla.suse.com/1191473
-
report
https://bugzilla.suse.com/1192267
-
web
https://www.suse.com/security/cve/CVE-2020-16590
-
web
https://www.suse.com/security/cve/CVE-2020-16591
-
web
https://www.suse.com/security/cve/CVE-2020-16592
-
web
https://www.suse.com/security/cve/CVE-2020-16593
-
web
https://www.suse.com/security/cve/CVE-2020-16598
-
web
https://www.suse.com/security/cve/CVE-2020-16599
-
web
https://www.suse.com/security/cve/CVE-2020-35448
-
web
https://www.suse.com/security/cve/CVE-2020-35493
-
web
https://www.suse.com/security/cve/CVE-2020-35496
-
web
https://www.suse.com/security/cve/CVE-2020-35507
-
web
https://www.suse.com/security/cve/CVE-2021-20197
-
web
https://www.suse.com/security/cve/CVE-2021-20284
-
web
https://www.suse.com/security/cve/CVE-2021-20294
-
web
https://www.suse.com/security/cve/CVE-2021-3487