CVE-2018-7208

In the coff_pointerize_aux function in coffgen.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, an index is not validated, which allows remote attackers to cause a denial of service (segmentation fault) or possibly have unspecified other impact via a crafted file, as demonstrated by objcopy of a COFF object.

In the coff_pointerize_aux function in coffgen.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, an index is not validated, which allows remote attackers to cause a denial of service (segmentation fault) or possibly have unspecified other impact via a crafted file, as demonstrated by objcopy of a COFF object.

• SECURITY UPDATE:
  • CVE-*.patch: backported many upstream patches to fix security issues.
  • CVE-2016-2226, CVE-2016-4487, CVE-2016-4488, CVE-2016-4489, CVE-2016-4490, CVE-2016-4492, CVE-2016-4493, CVE-2016-6131, CVE-2016-4491, CVE-2017-6965, CVE-2017-6966, CVE-2017-6969, CVE-2017-7209, CVE-2017-7210, CVE-2017-7223, CVE-2017-7224, CVE-2017-7225, CVE-2017-7226, CVE-2017-7227, CVE-2017-7299, CVE-2017-7300, CVE-2017-7301, CVE-2017-7302, CVE-2017-7614, CVE-2017-8393, CVE-2017-8394, CVE-2017-8395, CVE-2017-8397, CVE-2017-8396, CVE-2017-8398, CVE-2017-8421, CVE-2017-9038, CVE-2017-9039, CVE-2017-9040, CVE-2017-9042, CVE-2017-9041, CVE-2017-9044, CVE-2017-9742, CVE-2017-9744, CVE-2017-9752, CVE-2017-9745, CVE-2017-9746, CVE-2017-9747, CVE-2017-9748, CVE-2017-9749, CVE-2017-9750, CVE-2017-9751, CVE-2017-9753, CVE-2017-9754, CVE-2017-9755, CVE-2017-9756, CVE-2017-9954, CVE-2017-12448, CVE-2017-12449, CVE-2017-12455, CVE-2017-12457, CVE-2017-12458, CVE-2017-12459, CVE-2017-12450, CVE-2017-12452, CVE-2017-12453, CVE-2017-12454, CVE-2017-12456, CVE-2017-14333, CVE-2017-12451, CVE-2017-12799, CVE-2017-12967, CVE-2017-13710, CVE-2017-14128, CVE-2017-14129, CVE-2017-14130, CVE-2017-14529, CVE-2017-14930, CVE-2017-14932, CVE-2017-14938, CVE-2017-14939, CVE-2017-14940, CVE-2017-15020, CVE-2017-15021, CVE-2017-15022, CVE-2017-15024, CVE-2017-15025, CVE-2017-15225, CVE-2017-15938, CVE-2017-15939, CVE-2017-15996, CVE-2017-16826, CVE-2017-16827, CVE-2017-16828, CVE-2017-16831, CVE-2017-16832, CVE-2017-17080, CVE-2017-17121, CVE-2017-17123, CVE-2017-17124, CVE-2018-6323, CVE-2018-6543, CVE-2018-6759, CVE-2018-7208, CVE-2018-7568, CVE-2018-7569, CVE-2018-7642, CVE-2018-7643, CVE-2018-8945, CVE-2018-13033, CVE-2018-9138, CVE-2018-12641, CVE-2018-12697, CVE-2018-12698, CVE-2018-12699, CVE-2018-12700, CVE-2018-17794, CVE-2018-17985, CVE-2018-18484, CVE-2018-18700, CVE-2018-18701, CVE-2018-10372, CVE-2018-10373, CVE-2018-10534, CVE-2018-10535, CVE-2018-12934, CVE-2018-18483, CVE-2018-17358, CVE-2018-17359, CVE-2018-17360, CVE-2018-18309, CVE-2018-18605, CVE-2018-18606, CVE-2018-18607, CVE-2018-19931, CVE-2018-19932, CVE-2018-20002, CVE-2018-20623, CVE-2018-20671, CVE-2018-1000876, CVE-2017-17125, CVE-2019-9073, CVE-2019-9074, CVE-2019-9075, CVE-2019-9077, CVE-2019-9070, CVE-2019-9071, CVE-2019-12972, CVE-2019-14250, CVE-2019-14444, CVE-2019-17450, CVE-2019-17451

• CVE-2018-6323: Fix unsigned integer overflow
• CVE-2018-19931: Fix heap-based buffer overflow in bfd_elf32_swap_phdr_in
• CVE-2018-6543: Fix integer overflow
• CVE-2018-20671: Fix integer overflow vulnerability
• CVE-2018-6759: Fix segmentation fault
• CVE-2018-7208: Fix segmentation fault
• CVE-2018-7568: Fix integer overflow
• CVE-2018-7569: Fix integer underflow or overflow
• CVE-2018-7642: Fix aout_32_swap_std_reloc_out NULL pointer dereference
• CVE-2018-7643: Fix integer overflow
• CVE-2018-8945: Fix segmentation fault
• CVE-2018-13033: Fix excessive memory allocation
• CVE-2018-10373: Fix NULL pointer dereference
• CVE-2018-10535: Fix NULL pointer dereference
• CVE-2018-18309: Fix invalid memory address dereference
• CVE-2018-18605: Fix mishandles section merges
• CVE-2018-18606: Fix NULL pointer dereference
• CVE-2018-18607: Fix NULL pointer dereference in elf_link_input_bfd
• CVE-2018-19932: Fix integer overflow and infinite loop
• CVE-2018-20002: Fix memory consumption
• CVE-2018-20623: Fix use-after-free in the error function
• CVE-2018-1000876: Fix integer overflow trigger heap overflow
• CVE-2019-9073: Fix excessive memory allocation
• CVE-2019-9075: Fix heap-based buffer overflow in _bfd_archive_64_bit_slurp_armap
• CVE-2019-9077: Fix heap-based buffer overflow in process_mips_specific
• CVE-2019-12972: Fix heap-based buffer over-read in _bfd_doprnt
• CVE-2019-14444: Fix integer overflow
• CVE-2019-17450: Fix infinite recursion
• CVE-2016-2226: Fix integer overflow in the string_appends function in cplus-dem.c
• CVE-2016-4487: Fix use-after-free vulnerability in libiberty
• CVE-2016-4488: Fix use-after-free vulnerability in libiberty
• CVE-2016-4489: Fix integer overflow in libiberty
• CVE-2016-4490: Fix integer overflow in cp-demangle.c in libiberty
• CVE-2016-4492: Fix buffer overflow in the do_type function in cplus-dem.c in libiberty
• CVE-2016-4493: Fix out-of-bounds read in demangle_template_value_parm and do_hpacc_template_literal
• CVE-2016-6131: Fix infinite loop, stack overflow

• CVE-2018-6323: Fix unsigned integer overflow
• CVE-2018-19931: Fix heap-based buffer overflow in bfd_elf32_swap_phdr_in
• CVE-2018-6543: Fix integer overflow
• CVE-2018-20671: Fix integer overflow vulnerability
• CVE-2018-6759: Fix segmentation fault
• CVE-2018-7208: Fix segmentation fault
• CVE-2018-7568: Fix integer overflow
• CVE-2018-7569: Fix integer underflow or overflow
• CVE-2018-7642: Fix aout_32_swap_std_reloc_out NULL pointer dereference
• CVE-2018-7643: Fix integer overflow
• CVE-2018-8945: Fix segmentation fault
• CVE-2018-13033: Fix excessive memory allocation
• CVE-2018-10373: Fix NULL pointer dereference
• CVE-2018-10535: Fix NULL pointer dereference
• CVE-2018-18309: Fix invalid memory address dereference
• CVE-2018-18605: Fix mishandles section merges
• CVE-2018-18606: Fix NULL pointer dereference
• CVE-2018-18607: Fix NULL pointer dereference in elf_link_input_bfd
• CVE-2018-19932: Fix integer overflow and infinite loop
• CVE-2018-20002: Fix memory consumption
• CVE-2018-20623: Fix use-after-free in the error function
• CVE-2018-1000876: Fix integer overflow trigger heap overflow
• CVE-2019-9073: Fix excessive memory allocation
• CVE-2019-9075: Fix heap-based buffer overflow in _bfd_archive_64_bit_slurp_armap
• CVE-2019-9077: Fix heap-based buffer overflow in process_mips_specific
• CVE-2019-12972: Fix heap-based buffer over-read in _bfd_doprnt
• CVE-2019-14444: Fix integer overflow
• CVE-2019-17450: Fix infinite recursion
• CVE-2016-2226: Fix integer overflow in the string_appends function in cplus-dem.c
• CVE-2016-4487: Fix use-after-free vulnerability in libiberty
• CVE-2016-4488: Fix use-after-free vulnerability in libiberty
• CVE-2016-4489: Fix integer overflow in libiberty
• CVE-2016-4490: Fix integer overflow in cp-demangle.c in libiberty
• CVE-2016-4492: Fix buffer overflow in the do_type function in cplus-dem.c in libiberty
• CVE-2016-4493: Fix out-of-bounds read in demangle_template_value_parm and do_hpacc_template_literal
• CVE-2016-6131: Fix infinite loop, stack overflow

This update provides the latest stable binutils, currently version 2.32 and fixes at least the following security issues:

ihex.c in GNU Binutils before 2.26 contains a stack buffer overflow when printing bad bytes in Intel Hex objects (CVE-2014-9939)

Use-after-free vulnerability in libiberty allows remote attackers to cause a denial of service (segmentation fault and crash) via a crafted binary, related to "btypevec." (CVE-2016-4487)

Use-after-free vulnerability in libiberty allows remote attackers to cause a denial of service (segmentation fault and crash) via a crafted binary, related to "ktypevec." (CVE-2016-4488)

Integer overflow in the gnu_special function in libiberty allows remote attackers to cause a denial of service (segmentation fault and crash) via a crafted binary, related to the "demangling of virtual tables." (CVE-2016-4489)

Integer overflow in cp-demangle.c in libiberty allows remote attackers to cause a denial of service (segmentation fault and crash) via a crafted binary, related to inconsistent use of the long and int types for lengths. (CVE-2016-4490)

Buffer overflow in the do_type function in cplus-dem.c in libiberty allows remote attackers to cause a denial of service (segmentation fault and crash) via a crafted binary. (CVE-2016-4492)

The demangle_template_value_parm and do_hpacc_template_literal functions in cplus-dem.c in libiberty allow remote attackers to cause a denial of service (out-of-bounds read and crash) via a crafted binary. (CVE-2016-4493)

The demangler in GNU Libiberty allows remote attackers to cause a denial of service (infinite loop, stack overflow, and crash) via a cycle in the references of remembered mangled types. (CVE-2016-6131)

readelf in GNU Binutils 2.28 writes to illegal addresses while processing corrupt input files containing symbol-difference relocations, leading to a heap-based buffer overflow. (CVE-2017-6965)

readelf in GNU Binutils 2.28 has a use-after-free (specifically read-after-free) error while processing multiple, relocated sections in an MSP430 binary. This is caused by mishandling of an invalid symbol index, and mishandling of state across invocations. (CVE-2017-6966)

readelf in GNU Binutils 2.28 is vulnerable to a heap-based buffer over-read while processing corrupt RL78 binaries. The vulnerability can trigger program crashes. It may lead to an information leak as well. (CVE-2017-6969)

The dump_section_as_bytes function in readelf in GNU Binutils 2.28 accesses a NULL pointer while reading section contents in a corrupt binary, leading to a program crash. (CVE-2017-7209)

objdump in GNU Binutils 2.28 is vulnerable to multiple heap-based buffer over-reads (of size 1 and size 8) while handling corrupt STABS enum type strings in a crafted object file, leading to program crash. (CVE-2017-7210)

GNU assembler in GNU Binutils 2.28 is vulnerable to a global buffer overflow (of size 1) while attempting to unget an EOF character from the input stream, potentially leading to a program crash. (CVE-2017-7223)

The find_nearest_line function in objdump in GNU Binutils 2.28 is vulnerable to an invalid write (of size 1) while disassembling a corrupt binary that contains an empty function name, leading to a program crash. (CVE-2017-7224)

The find_nearest_line function in addr2line in GNU Binutils 2.28 does not handle the case where the main file name and the directory name are both empty, triggering a NULL pointer dereference and an invalid write, and leading to a program crash. (CVE-2017-7225)

The pe_ILF_object_p function in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, is vulnerable to a heap-based buffer over-read of size 4049 because it uses the strlen function instead of strnlen, leading to program crashes in several utilities such as addr2line, size, and strings. It could lead to information disclosure as well. (CVE-2017-7226)

GNU linker (ld) in GNU Binutils 2.28 is vulnerable to a heap-based buffer overflow while…

This update for binutils fixes the following issues:

binutils was updated to current 2.32 branch [jsc#ECO-368].

Includes following security fixes:

• CVE-2018-17358: Fixed invalid memory access in _bfd_stab_section_find_nearest_line in syms.c (bsc#1109412)

• CVE-2018-17359: Fixed invalid memory access exists in bfd_zalloc in opncls.c (bsc#1109413)

• CVE-2018-17360: Fixed heap-based buffer over-read in bfd_getl32 in libbfd.c (bsc#1109414)

• CVE-2018-17985: Fixed a stack consumption problem caused by the cplus_demangle_type (bsc#1116827)

• CVE-2018-18309: Fixed an invalid memory address dereference was discovered in read_reloc in reloc.c (bsc#1111996)

• CVE-2018-18483: Fixed get_count function provided by libiberty that allowed attackers to cause a denial of service or other unspecified impact (bsc#1112535)

• CVE-2018-18484: Fixed stack exhaustion in the C++ demangling functions provided by libiberty, caused by recursive stack frames (bsc#1112534)

• CVE-2018-18605: Fixed a heap-based buffer over-read issue was discovered in the function sec_merge_hash_lookup causing a denial of service (bsc#1113255)

• CVE-2018-18606: Fixed a NULL pointer dereference in _bfd_add_merge_section when attempting to merge sections with large alignments, causing denial of service (bsc#1113252)

• CVE-2018-18607: Fixed a NULL pointer dereference in elf_link_input_bfd when used for finding STT_TLS symbols without any TLS section, causing denial of service (bsc#1113247)

• CVE-2018-19931: Fixed a heap-based buffer overflow in bfd_elf32_swap_phdr_in in elfcode.h (bsc#1118831)

• CVE-2018-19932: Fixed an integer overflow and infinite loop caused by the IS_CONTAINED_BY_LMA (bsc#1118830)

• CVE-2018-20623: Fixed a use-after-free in the error function in elfcomm.c (bsc#1121035)

• CVE-2018-20651: Fixed a denial of service via a NULL pointer dereference in elf_link_add_object_symbols in elflink.c (bsc#1121034)

• CVE-2018-20671: Fixed an integer overflow that can trigger a heap-based buffer overflow in load_specific_debug_section in objdump.c (bsc#1121056)

• CVE-2018-1000876: Fixed integer overflow in bfd_get_dynamic_reloc_upper_bound,bfd_canonicalize_dynamic_reloc in objdump (bsc#1120640)

• CVE-2019-1010180: Fixed an out of bound memory access that could lead to crashes (bsc#1142772)

• enable xtensa architecture (Tensilica lc6 and related)

• Use -ffat-lto-objects in order to provide assembly for static libs (bsc#1141913).

• Fixed some LTO build issues (bsc#1133131 bsc#1133232).

• riscv: Don't check ABI flags if no code section

• Fixed a segfault in ld when building some versions of pacemaker (bsc#1154025, bsc#1154016).

• Add avr, epiphany and rx to target_list so that the common binutils can handle all objects we can create with crosses (bsc#1152590).

Update to binutils 2.32:

• The binutils now support for the C-SKY processor series.
• The x86 assembler now supports a -mvexwig=[0|1] option to control encoding of VEX.W-ignored (WIG) VEX instructions. It also has a new -mx86-used-note=[yes|no] option to generate (or not) x86 GNU property notes.
• The MIPS assembler now supports the Loongson EXTensions R2 (EXT2), the Loongson EXTensions (EXT) instructions, the Loongson Content Address Memory (CAM) ASE and the Loongson MultiMedia extensions Instructions (MMI) ASE.
• The addr2line, c++filt, nm and objdump tools now have a default limit on the maximum amount of recursion that is allowed whilst demangling strings. This limit can be disabled if necessary.
• Objdump's --disassemble option can now take a parameter, specifying the starting symbol for disassembly. Disassembly will continue from this symbol up to the next symbol or the end of the function.
• The BFD linker will now report property change in linker map file when merging GNU properties.
• The BFD linker's -t option now doesn't report members within archives, unless -t is given twice. This makes it more useful when generating a list of files that should be packaged for a …

This update for binutils fixes the following issues:

binutils was updated to current 2.32 branch [jsc#ECO-368].

Includes following security fixes:

• CVE-2018-17358: Fixed invalid memory access in _bfd_stab_section_find_nearest_line in syms.c (bsc#1109412)

• CVE-2018-17359: Fixed invalid memory access exists in bfd_zalloc in opncls.c (bsc#1109413)

• CVE-2018-17360: Fixed heap-based buffer over-read in bfd_getl32 in libbfd.c (bsc#1109414)

• CVE-2018-17985: Fixed a stack consumption problem caused by the cplus_demangle_type (bsc#1116827)

• CVE-2018-18309: Fixed an invalid memory address dereference was discovered in read_reloc in reloc.c (bsc#1111996)

• CVE-2018-18483: Fixed get_count function provided by libiberty that allowed attackers to cause a denial of service or other unspecified impact (bsc#1112535)

• CVE-2018-18484: Fixed stack exhaustion in the C++ demangling functions provided by libiberty, caused by recursive stack frames (bsc#1112534)

• CVE-2018-18605: Fixed a heap-based buffer over-read issue was discovered in the function sec_merge_hash_lookup causing a denial of service (bsc#1113255)

• CVE-2018-18606: Fixed a NULL pointer dereference in _bfd_add_merge_section when attempting to merge sections with large alignments, causing denial of service (bsc#1113252)

• CVE-2018-18607: Fixed a NULL pointer dereference in elf_link_input_bfd when used for finding STT_TLS symbols without any TLS section, causing denial of service (bsc#1113247)

• CVE-2018-19931: Fixed a heap-based buffer overflow in bfd_elf32_swap_phdr_in in elfcode.h (bsc#1118831)

• CVE-2018-19932: Fixed an integer overflow and infinite loop caused by the IS_CONTAINED_BY_LMA (bsc#1118830)

• CVE-2018-20623: Fixed a use-after-free in the error function in elfcomm.c (bsc#1121035)

• CVE-2018-20651: Fixed a denial of service via a NULL pointer dereference in elf_link_add_object_symbols in elflink.c (bsc#1121034)

• CVE-2018-20671: Fixed an integer overflow that can trigger a heap-based buffer overflow in load_specific_debug_section in objdump.c (bsc#1121056)

• CVE-2018-1000876: Fixed integer overflow in bfd_get_dynamic_reloc_upper_bound,bfd_canonicalize_dynamic_reloc in objdump (bsc#1120640)

• CVE-2019-1010180: Fixed an out of bound memory access that could lead to crashes (bsc#1142772)

• enable xtensa architecture (Tensilica lc6 and related)

• Use -ffat-lto-objects in order to provide assembly for static libs (bsc#1141913).

• Fixed some LTO build issues (bsc#1133131 bsc#1133232).

• riscv: Don't check ABI flags if no code section

• Fixed a segfault in ld when building some versions of pacemaker (bsc#1154025, bsc#1154016).

• Add avr, epiphany and rx to target_list so that the common binutils can handle all objects we can create with crosses (bsc#1152590).

Update to binutils 2.32:

• The binutils now support for the C-SKY processor series.
• The x86 assembler now supports a -mvexwig=[0|1] option to control encoding of VEX.W-ignored (WIG) VEX instructions. It also has a new -mx86-used-note=[yes|no] option to generate (or not) x86 GNU property notes.
• The MIPS assembler now supports the Loongson EXTensions R2 (EXT2), the Loongson EXTensions (EXT) instructions, the Loongson Content Address Memory (CAM) ASE and the Loongson MultiMedia extensions Instructions (MMI) ASE.
• The addr2line, c++filt, nm and objdump tools now have a default limit on the maximum amount of recursion that is allowed whilst demangling strings. This limit can be disabled if necessary.
• Objdump's --disassemble option can now take a parameter, specifying the starting symbol for disassembly. Disassembly will continue from this symbol up to the next symbol or the end of the function.
• The BFD linker will now report property change in linker map file when merging GNU properties.
• The BFD linker's -t option now doesn't report members within archives, unless -t is given twice. This makes it more useful when generating a list of files that should be packaged for a …

These are all security issues fixed in the binutils-2.37-1.3 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the gdb-12.1-6.1 package on the GA media of openSUSE Tumbleweed.

This update for binutils to version 2.31 fixes the following issues:

These security issues were fixed:

• CVE-2017-15996: readelf allowed remote attackers to cause a denial of service (excessive memory allocation) or possibly have unspecified other impact via a crafted ELF file that triggered a buffer overflow on fuzzed archive header (bsc#1065643)
• CVE-2017-15939: Binary File Descriptor (BFD) library (aka libbfd) mishandled NULL files in a .debug_line file table, which allowed remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted ELF file, related to concat_filename (bsc#1065689)
• CVE-2017-15938: the Binary File Descriptor (BFD) library (aka libbfd) miscalculated DW_FORM_ref_addr die refs in the case of a relocatable object file, which allowed remote attackers to cause a denial of service (find_abstract_instance_name invalid memory read, segmentation fault, and application crash) (bsc#1065693)
• CVE-2017-16826: The coff_slurp_line_table function the Binary File Descriptor (BFD) library (aka libbfd) allowed remote attackers to cause a denial of service (invalid memory access and application crash) or possibly have unspecified other impact via a crafted PE file (bsc#1068640)
• CVE-2017-16832: The pe_bfd_read_buildid function in the Binary File Descriptor (BFD) library (aka libbfd) did not validate size and offset values in the data dictionary, which allowed remote attackers to cause a denial of service (segmentation violation and application crash) or possibly have unspecified other impact via a crafted PE file (bsc#1068643)
• CVE-2017-16831: Binary File Descriptor (BFD) library (aka libbfd) did not validate the symbol count, which allowed remote attackers to cause a denial of service (integer overflow and application crash, or excessive memory allocation) or possibly have unspecified other impact via a crafted PE file (bsc#1068887)
• CVE-2017-16830: The print_gnu_property_note function did not have integer-overflow protection on 32-bit platforms, which allowed remote attackers to cause a denial of service (segmentation violation and application crash) or possibly have unspecified other impact via a crafted ELF file (bsc#1068888)
• CVE-2017-16829: The _bfd_elf_parse_gnu_properties function in the Binary File Descriptor (BFD) library (aka libbfd) did not prevent negative pointers, which allowed remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a crafted ELF file (bsc#1068950)
• CVE-2017-16828: The display_debug_frames function allowed remote attackers to cause a denial of service (integer overflow and heap-based buffer over-read, and application crash) or possibly have unspecified other impact via a crafted ELF file (bsc#1069176)
• CVE-2017-16827: The aout_get_external_symbols function in the Binary File Descriptor (BFD) library (aka libbfd) allowed remote attackers to cause a denial of service (slurp_symtab invalid free and application crash) or possibly have unspecified other impact via a crafted ELF file (bsc#1069202)
• CVE-2018-6323: The elf_object_p function in the Binary File Descriptor (BFD) library (aka libbfd) had an unsigned integer overflow because bfd_size_type multiplication is not used. A crafted ELF file allowed remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact (bsc#1077745)
• CVE-2018-6543: Prevent integer overflow in the function load_specific_debug_section() which resulted in malloc() with 0 size. A crafted ELF file allowed remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact (bsc#1079103)
• CVE-2018-6759: The bfd_get_debug_link_info_1 function in the Binary File Descriptor (BFD) library (aka libbfd) had an unchecked strnlen operation. Remote attackers could have…

This update for binutils to 2.31 fixes the following issues:

These security issues were fixed:

• CVE-2017-15996: readelf allowed remote attackers to cause a denial of service (excessive memory allocation) or possibly have unspecified other impact via a crafted ELF file that triggered a buffer overflow on fuzzed archive header (bsc#1065643).
• CVE-2017-15939: Binary File Descriptor (BFD) library (aka libbfd) mishandled NULL files in a .debug_line file table, which allowed remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted ELF file, related to concat_filename (bsc#1065689).
• CVE-2017-15938: the Binary File Descriptor (BFD) library (aka libbfd) miscalculated DW_FORM_ref_addr die refs in the case of a relocatable object file, which allowed remote attackers to cause a denial of service (find_abstract_instance_name invalid memory read, segmentation fault, and application crash) (bsc#1065693).
• CVE-2017-16826: The coff_slurp_line_table function the Binary File Descriptor (BFD) library (aka libbfd) allowed remote attackers to cause a denial of service (invalid memory access and application crash) or possibly have unspecified other impact via a crafted PE file (bsc#1068640).
• CVE-2017-16832: The pe_bfd_read_buildid function in the Binary File Descriptor (BFD) library (aka libbfd) did not validate size and offset values in the data dictionary, which allowed remote attackers to cause a denial of service (segmentation violation and application crash) or possibly have unspecified other impact via a crafted PE file (bsc#1068643).
• CVE-2017-16831: Binary File Descriptor (BFD) library (aka libbfd) did not validate the symbol count, which allowed remote attackers to cause a denial of service (integer overflow and application crash, or excessive memory allocation) or possibly have unspecified other impact via a crafted PE file (bsc#1068887).
• CVE-2017-16830: The print_gnu_property_note function did not have integer-overflow protection on 32-bit platforms, which allowed remote attackers to cause a denial of service (segmentation violation and application crash) or possibly have unspecified other impact via a crafted ELF file (bsc#1068888).
• CVE-2017-16829: The _bfd_elf_parse_gnu_properties function in the Binary File Descriptor (BFD) library (aka libbfd) did not prevent negative pointers, which allowed remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a crafted ELF file (bsc#1068950).
• CVE-2017-16828: The display_debug_frames function allowed remote attackers to cause a denial of service (integer overflow and heap-based buffer over-read, and application crash) or possibly have unspecified other impact via a crafted ELF file (bsc#1069176).
• CVE-2017-16827: The aout_get_external_symbols function in the Binary File Descriptor (BFD) library (aka libbfd) allowed remote attackers to cause a denial of service (slurp_symtab invalid free and application crash) or possibly have unspecified other impact via a crafted ELF file (bsc#1069202).
• CVE-2018-6323: The elf_object_p function in the Binary File Descriptor (BFD) library (aka libbfd) had an unsigned integer overflow because bfd_size_type multiplication is not used. A crafted ELF file allowed remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact (bsc#1077745).
• CVE-2018-6543: Prevent integer overflow in the function load_specific_debug_section() which resulted in malloc() with 0 size. A crafted ELF file allowed remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact (bsc#1079103).
• CVE-2018-6759: The bfd_get_debug_link_info_1 function in the Binary File Descriptor (BFD) library (aka libbfd) had an unchecked strnlen operation. Remote attackers could have…

This update for binutils to 2.31 fixes the following issues:

These security issues were fixed:

• CVE-2017-15996: readelf allowed remote attackers to cause a denial of service (excessive memory allocation) or possibly have unspecified other impact via a crafted ELF file that triggered a buffer overflow on fuzzed archive header (bsc#1065643).
• CVE-2017-15939: Binary File Descriptor (BFD) library (aka libbfd) mishandled NULL files in a .debug_line file table, which allowed remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted ELF file, related to concat_filename (bsc#1065689).
• CVE-2017-15938: the Binary File Descriptor (BFD) library (aka libbfd) miscalculated DW_FORM_ref_addr die refs in the case of a relocatable object file, which allowed remote attackers to cause a denial of service (find_abstract_instance_name invalid memory read, segmentation fault, and application crash) (bsc#1065693).
• CVE-2017-16826: The coff_slurp_line_table function the Binary File Descriptor (BFD) library (aka libbfd) allowed remote attackers to cause a denial of service (invalid memory access and application crash) or possibly have unspecified other impact via a crafted PE file (bsc#1068640).
• CVE-2017-16832: The pe_bfd_read_buildid function in the Binary File Descriptor (BFD) library (aka libbfd) did not validate size and offset values in the data dictionary, which allowed remote attackers to cause a denial of service (segmentation violation and application crash) or possibly have unspecified other impact via a crafted PE file (bsc#1068643).
• CVE-2017-16831: Binary File Descriptor (BFD) library (aka libbfd) did not validate the symbol count, which allowed remote attackers to cause a denial of service (integer overflow and application crash, or excessive memory allocation) or possibly have unspecified other impact via a crafted PE file (bsc#1068887).
• CVE-2017-16830: The print_gnu_property_note function did not have integer-overflow protection on 32-bit platforms, which allowed remote attackers to cause a denial of service (segmentation violation and application crash) or possibly have unspecified other impact via a crafted ELF file (bsc#1068888).
• CVE-2017-16829: The _bfd_elf_parse_gnu_properties function in the Binary File Descriptor (BFD) library (aka libbfd) did not prevent negative pointers, which allowed remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a crafted ELF file (bsc#1068950).
• CVE-2017-16828: The display_debug_frames function allowed remote attackers to cause a denial of service (integer overflow and heap-based buffer over-read, and application crash) or possibly have unspecified other impact via a crafted ELF file (bsc#1069176).
• CVE-2017-16827: The aout_get_external_symbols function in the Binary File Descriptor (BFD) library (aka libbfd) allowed remote attackers to cause a denial of service (slurp_symtab invalid free and application crash) or possibly have unspecified other impact via a crafted ELF file (bsc#1069202).
• CVE-2018-6323: The elf_object_p function in the Binary File Descriptor (BFD) library (aka libbfd) had an unsigned integer overflow because bfd_size_type multiplication is not used. A crafted ELF file allowed remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact (bsc#1077745).
• CVE-2018-6543: Prevent integer overflow in the function load_specific_debug_section() which resulted in malloc() with 0 size. A crafted ELF file allowed remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact (bsc#1079103).
• CVE-2018-6759: The bfd_get_debug_link_info_1 function in the Binary File Descriptor (BFD) library (aka libbfd) had an unchecked strnlen operation. Remote attackers could have…

This update for binutils fixes the following issues:

binutils was updated to current 2.32 branch [jsc#ECO-368].

Includes following security fixes:

• CVE-2018-17358: Fixed invalid memory access in _bfd_stab_section_find_nearest_line in syms.c (bsc#1109412)

• CVE-2018-17359: Fixed invalid memory access exists in bfd_zalloc in opncls.c (bsc#1109413)

• CVE-2018-17360: Fixed heap-based buffer over-read in bfd_getl32 in libbfd.c (bsc#1109414)

• CVE-2018-17985: Fixed a stack consumption problem caused by the cplus_demangle_type (bsc#1116827)

• CVE-2018-18309: Fixed an invalid memory address dereference was discovered in read_reloc in reloc.c (bsc#1111996)

• CVE-2018-18483: Fixed get_count function provided by libiberty that allowed attackers to cause a denial of service or other unspecified impact (bsc#1112535)

• CVE-2018-18484: Fixed stack exhaustion in the C++ demangling functions provided by libiberty, caused by recursive stack frames (bsc#1112534)

• CVE-2018-18605: Fixed a heap-based buffer over-read issue was discovered in the function sec_merge_hash_lookup causing a denial of service (bsc#1113255)

• CVE-2018-18606: Fixed a NULL pointer dereference in _bfd_add_merge_section when attempting to merge sections with large alignments, causing denial of service (bsc#1113252)

• CVE-2018-18607: Fixed a NULL pointer dereference in elf_link_input_bfd when used for finding STT_TLS symbols without any TLS section, causing denial of service (bsc#1113247)

• CVE-2018-19931: Fixed a heap-based buffer overflow in bfd_elf32_swap_phdr_in in elfcode.h (bsc#1118831)

• CVE-2018-19932: Fixed an integer overflow and infinite loop caused by the IS_CONTAINED_BY_LMA (bsc#1118830)

• CVE-2018-20623: Fixed a use-after-free in the error function in elfcomm.c (bsc#1121035)

• CVE-2018-20651: Fixed a denial of service via a NULL pointer dereference in elf_link_add_object_symbols in elflink.c (bsc#1121034)

• CVE-2018-20671: Fixed an integer overflow that can trigger a heap-based buffer overflow in load_specific_debug_section in objdump.c (bsc#1121056)

• CVE-2018-1000876: Fixed integer overflow in bfd_get_dynamic_reloc_upper_bound,bfd_canonicalize_dynamic_reloc in objdump (bsc#1120640)

• CVE-2019-1010180: Fixed an out of bound memory access that could lead to crashes (bsc#1142772)

• enable xtensa architecture (Tensilica lc6 and related)

• Use -ffat-lto-objects in order to provide assembly for static libs (bsc#1141913).

• Fixed some LTO build issues (bsc#1133131 bsc#1133232).

• riscv: Don't check ABI flags if no code section

• Fixed a segfault in ld when building some versions of pacemaker (bsc#1154025, bsc#1154016).

• Add avr, epiphany and rx to target_list so that the common binutils can handle all objects we can create with crosses (bsc#1152590).

Update to binutils 2.32:

• The binutils now support for the C-SKY processor series.
• The x86 assembler now supports a -mvexwig=[0|1] option to control encoding of VEX.W-ignored (WIG) VEX instructions. It also has a new -mx86-used-note=[yes|no] option to generate (or not) x86 GNU property notes.
• The MIPS assembler now supports the Loongson EXTensions R2 (EXT2), the Loongson EXTensions (EXT) instructions, the Loongson Content Address Memory (CAM) ASE and the Loongson MultiMedia extensions Instructions (MMI) ASE.
• The addr2line, c++filt, nm and objdump tools now have a default limit on the maximum amount of recursion that is allowed whilst demangling strings. This limit can be disabled if necessary.
• Objdump's --disassemble option can now take a parameter, specifying the starting symbol for disassembly. Disassembly will continue from this symbol up to the next symbol or the end of the function.
• The BFD linker will now report property change in linker map file when merging GNU properties.
• The BFD linker's -t option now doesn't report members within archives, unless -t is given twice. This makes it more useful when generating a list of files that should be packaged for a …

This update for binutils fixes the following issues:

binutils was updated to current 2.32 branch [jsc#ECO-368].

Includes following security fixes:

• CVE-2018-17358: Fixed invalid memory access in _bfd_stab_section_find_nearest_line in syms.c (bsc#1109412)

• CVE-2018-17359: Fixed invalid memory access exists in bfd_zalloc in opncls.c (bsc#1109413)

• CVE-2018-17360: Fixed heap-based buffer over-read in bfd_getl32 in libbfd.c (bsc#1109414)

• CVE-2018-17985: Fixed a stack consumption problem caused by the cplus_demangle_type (bsc#1116827)

• CVE-2018-18309: Fixed an invalid memory address dereference was discovered in read_reloc in reloc.c (bsc#1111996)

• CVE-2018-18483: Fixed get_count function provided by libiberty that allowed attackers to cause a denial of service or other unspecified impact (bsc#1112535)

• CVE-2018-18484: Fixed stack exhaustion in the C++ demangling functions provided by libiberty, caused by recursive stack frames (bsc#1112534)

• CVE-2018-18605: Fixed a heap-based buffer over-read issue was discovered in the function sec_merge_hash_lookup causing a denial of service (bsc#1113255)

• CVE-2018-18606: Fixed a NULL pointer dereference in _bfd_add_merge_section when attempting to merge sections with large alignments, causing denial of service (bsc#1113252)

• CVE-2018-18607: Fixed a NULL pointer dereference in elf_link_input_bfd when used for finding STT_TLS symbols without any TLS section, causing denial of service (bsc#1113247)

• CVE-2018-19931: Fixed a heap-based buffer overflow in bfd_elf32_swap_phdr_in in elfcode.h (bsc#1118831)

• CVE-2018-19932: Fixed an integer overflow and infinite loop caused by the IS_CONTAINED_BY_LMA (bsc#1118830)

• CVE-2018-20623: Fixed a use-after-free in the error function in elfcomm.c (bsc#1121035)

• CVE-2018-20651: Fixed a denial of service via a NULL pointer dereference in elf_link_add_object_symbols in elflink.c (bsc#1121034)

• CVE-2018-20671: Fixed an integer overflow that can trigger a heap-based buffer overflow in load_specific_debug_section in objdump.c (bsc#1121056)

• CVE-2018-1000876: Fixed integer overflow in bfd_get_dynamic_reloc_upper_bound,bfd_canonicalize_dynamic_reloc in objdump (bsc#1120640)

• CVE-2019-1010180: Fixed an out of bound memory access that could lead to crashes (bsc#1142772)

• enable xtensa architecture (Tensilica lc6 and related)

• Use -ffat-lto-objects in order to provide assembly for static libs (bsc#1141913).

• Fixed some LTO build issues (bsc#1133131 bsc#1133232).

• riscv: Don't check ABI flags if no code section

• Fixed a segfault in ld when building some versions of pacemaker (bsc#1154025, bsc#1154016).

• Add avr, epiphany and rx to target_list so that the common binutils can handle all objects we can create with crosses (bsc#1152590).

Update to binutils 2.32:

• The binutils now support for the C-SKY processor series.
• The x86 assembler now supports a -mvexwig=[0|1] option to control encoding of VEX.W-ignored (WIG) VEX instructions. It also has a new -mx86-used-note=[yes|no] option to generate (or not) x86 GNU property notes.
• The MIPS assembler now supports the Loongson EXTensions R2 (EXT2), the Loongson EXTensions (EXT) instructions, the Loongson Content Address Memory (CAM) ASE and the Loongson MultiMedia extensions Instructions (MMI) ASE.
• The addr2line, c++filt, nm and objdump tools now have a default limit on the maximum amount of recursion that is allowed whilst demangling strings. This limit can be disabled if necessary.
• Objdump's --disassemble option can now take a parameter, specifying the starting symbol for disassembly. Disassembly will continue from this symbol up to the next symbol or the end of the function.
• The BFD linker will now report property change in linker map file when merging GNU properties.
• The BFD linker's -t option now doesn't report members within archives, unless -t is given twice. This makes it more useful when generating a list of files that should be packaged for a …

This update for gdb fixes the following issues:

gdb was updated to 12.1. (jsc#SLE-21561)

• DBX mode is deprecated, and will be removed in GDB 13.

• GDB 12 is the last release of GDB that will support building against Python 2. From GDB 13, it will only be possible to build GDB itself with Python 3 support.

• Improved C++ template support:

  GDB now treats functions/types involving C++ templates like it does function overloads. Users may omit parameter lists to set breakpoints on families of template functions, including types/functions composed of multiple template types: (gdb) break template_func(template_1, int) The above will set breakpoints at every function template_func' where the first function parameter is any template type named template_1' and the second function parameter is `int'. TAB completion also gains similar improvements.

• New commands:

  • maint set backtrace-on-fatal-signal on|off
  • maint show backtrace-on-fatal-signal

  This setting is 'on' by default. When 'on' GDB will print a limited backtrace to stderr in the situation where GDB terminates with a fatal signal. This only supported on some platforms where the backtrace and backtrace_symbols_fd functions are available.

  • set source open on|off
  • show source open

  This setting, which is on by default, controls whether GDB will try to open source code files. Switching this off will stop GDB trying to open and read source code files, which can be useful if the files are located over a slow network connection.

  • set varsize-limit
  • show varsize-limit

  These are now deprecated aliases for 'set max-value-size' and 'show max-value-size'.

  • task apply [all | TASK-IDS...] [FLAG]... COMMAND

  Like 'thread apply', but applies COMMAND to Ada tasks.

  • watch [...] task ID

  Watchpoints can now be restricted to a specific Ada task.

  • maint set internal-error backtrace on|off
  • maint show internal-error backtrace
  • maint set internal-warning backtrace on|off
  • maint show internal-warning backtrace

  GDB can now print a backtrace of itself when it encounters either an internal-error, or an internal-warning. This is on by default for internal-error and off by default for internal-warning.

  • set logging on|off

  Deprecated and replaced by 'set logging enabled on|off'.

  • set logging enabled on|off
  • show logging enabled

  These commands set or show whether logging is enabled or disabled.

  • exit

  You can now exit GDB by using the new command 'exit', in addition to the existing 'quit' command.

  • set debug threads on|off
  • show debug threads

  Print additional debug messages about thread creation and deletion.

  • set debug linux-nat on|off
  • show debug linux-nat

  These new commands replaced the old 'set debug lin-lwp' and 'show debug lin-lwp' respectively. Turning this setting on prints debug messages relating to GDB's handling of native Linux inferiors.

  • maint flush source-cache

  Flush the contents of the source code cache.

  • maint set gnu-source-highlight enabled on|off
  • maint show gnu-source-highlight enabled

  Whether GDB should use the GNU Source Highlight library for adding styling to source code. When off, the library will not be used, even when available. When GNU Source Highlight isn't used, or can't add styling to a particular source file, then the Python Pygments library will be used instead.

  • set suppress-cli-notifications (on|off)
  • show suppress-cli-notifications

  This controls whether printing the notifications is suppressed for CLI. CLI notifications occur when you change the selected context (i.e., the current inferior, thread and/or the frame), or when the program being debugged stops (e.g., because of hitting a breakpoint, completing source-stepping, an interrupt, etc.).

  • set style disassembler enabled on|off
  • show style disassembler enabled

  If GDB is compiled with Python support, and the…

This update for gdb fixes the following issues:

• Drop libdebuginfod1 BuildRequires/Recommends. The former isn't needed because there's a build requirement on libdebuginfod-devel already, which will pull the shared library. And the latter, because it's bogus since RPM auto generated dependency will take care of that requirement.

gdb was released in 13.2:

• This version of GDB includes the following changes and enhancements:

  • Support for the following new targets has been added in both GDB and GDBserver:

    * GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*
    * GNU/Linux/CSKY (gdbserver) csky*-*linux* 
    

  • The Windows native target now supports target async.

  • Floating-point support has now been added on LoongArch GNU/Linux.

  • New commands:

    * set print nibbles [on|off]
    * show print nibbles
    
    * This controls whether the 'print/t' command will display binary values in groups of four bits, known as 'nibbles'. The default is 'off'.
      Various styling-related commands. See the gdb/NEWS file for more details.
      Various maintenance commands. These are normally aimed at GDB experts or developers. See the gdb/NEWS file for more details. 
    

  • Python API improvements:

      * New Python API for instruction disassembly.
    
      * The new attribute 'locations' of gdb.Breakpoint returns a list of gdb.BreakpointLocation objects specifying the locations where the breakpoint is inserted into the debuggee.
      * New Python type gdb.BreakpointLocation.
      * New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE) that formats ADDRESS as 'address '
      * New function gdb.current_language that returns the name of the current language. Unlike gdb.parameter('language'), this will never return 'auto'.
      * New function gdb.print_options that returns a dictionary of the prevailing print options, in the form accepted by gdb.Value.format_string.
      * New method gdb.Frame.language that returns the name of the frame's language.
      * gdb.Value.format_string now uses the format provided by 'print', if it is called during a 'print' or other similar operation.
      * gdb.Value.format_string now accepts the 'summary' keyword. This can be used to request a shorter representation of a value, the way that 'set print frame-arguments scalars' does.
      * The gdb.register_window_type method now restricts the set of acceptable window names. The first character of a window's name must start with a character in the set [a-zA-Z], every subsequent character of a window's name must be in the set [-_.a-zA-Z0-9]. 
    

  • GDB/MI changes:

     * MI version 1 is deprecated, and will be removed in GDB 14.
     * The async record stating the stopped reason 'breakpoint-hit' now contains an optional field locno. 
    

  • Miscellaneous improvements:

     * gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for ELF.
     * New convenience variable $_inferior_thread_count contains the number of live threads in the current inferior.
     * New convenience variables $_hit_bpnum and $_hit_locno, set to the breakpoint number and the breakpoint location number of the breakpoint last hit.
     * The 'info breakpoints' now displays enabled breakpoint locations of disabled breakpoints as in the 'y-' state.
     * The format of 'disassemble /r' and 'record instruction-history /r' has changed to match the layout of GNU objdump when disassembling.
    
     * A new format '/b' has been introduce to provide the old behavior of '/r'.
     * The TUI no longer styles the source and assembly code highlighted by the current position indicator by default. You can however re-enable styling using the new 'set style tui-current-position' command.
     * It is now possible to use the 'document' command to document user-defined commands.
     * Support for memory tag data for AArch64 MTE. 
    

  *…

This update for gdb fixes the following issues:

• Drop libdebuginfod1 BuildRequires/Recommends. The former isn't needed because there's a build requirement on libdebuginfod-devel already, which will pull the shared library. And the latter, because it's bogus since RPM auto generated dependency will take care of that requirement.

gdb was released in 13.2:

• This version of GDB includes the following changes and enhancements:

  • Support for the following new targets has been added in both GDB and GDBserver:

    * GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*
    * GNU/Linux/CSKY (gdbserver) csky*-*linux* 
    

  • The Windows native target now supports target async.

  • Floating-point support has now been added on LoongArch GNU/Linux.

  • New commands:

    * set print nibbles [on|off]
    * show print nibbles
    
    * This controls whether the 'print/t' command will display binary values in groups of four bits, known as 'nibbles'. The default is 'off'.
      Various styling-related commands. See the gdb/NEWS file for more details.
      Various maintenance commands. These are normally aimed at GDB experts or developers. See the gdb/NEWS file for more details. 
    

  • Python API improvements:

      * New Python API for instruction disassembly.
    
      * The new attribute 'locations' of gdb.Breakpoint returns a list of gdb.BreakpointLocation objects specifying the locations where the breakpoint is inserted into the debuggee.
      * New Python type gdb.BreakpointLocation.
      * New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE) that formats ADDRESS as 'address '
      * New function gdb.current_language that returns the name of the current language. Unlike gdb.parameter('language'), this will never return 'auto'.
      * New function gdb.print_options that returns a dictionary of the prevailing print options, in the form accepted by gdb.Value.format_string.
      * New method gdb.Frame.language that returns the name of the frame's language.
      * gdb.Value.format_string now uses the format provided by 'print', if it is called during a 'print' or other similar operation.
      * gdb.Value.format_string now accepts the 'summary' keyword. This can be used to request a shorter representation of a value, the way that 'set print frame-arguments scalars' does.
      * The gdb.register_window_type method now restricts the set of acceptable window names. The first character of a window's name must start with a character in the set [a-zA-Z], every subsequent character of a window's name must be in the set [-_.a-zA-Z0-9]. 
    

  • GDB/MI changes:

     * MI version 1 is deprecated, and will be removed in GDB 14.
     * The async record stating the stopped reason 'breakpoint-hit' now contains an optional field locno. 
    

  • Miscellaneous improvements:

     * gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for ELF.
     * New convenience variable $_inferior_thread_count contains the number of live threads in the current inferior.
     * New convenience variables $_hit_bpnum and $_hit_locno, set to the breakpoint number and the breakpoint location number of the breakpoint last hit.
     * The 'info breakpoints' now displays enabled breakpoint locations of disabled breakpoints as in the 'y-' state.
     * The format of 'disassemble /r' and 'record instruction-history /r' has changed to match the layout of GNU objdump when disassembling.
    
     * A new format '/b' has been introduce to provide the old behavior of '/r'.
     * The TUI no longer styles the source and assembly code highlighted by the current position indicator by default. You can however re-enable styling using the new 'set style tui-current-position' command.
     * It is now possible to use the 'document' command to document user-defined commands.
     * Support for memory tag data for AArch64 MTE. 
    

  *…

This update for gdb fixes the following issues:

• Drop libdebuginfod1 BuildRequires/Recommends. The former isn't needed because there's a build requirement on libdebuginfod-devel already, which will pull the shared library. And the latter, because it's bogus since RPM auto generated dependency will take care of that requirement.

gdb was released in 13.2:

• This version of GDB includes the following changes and enhancements:

  • Support for the following new targets has been added in both GDB and GDBserver:

    * GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*
    * GNU/Linux/CSKY (gdbserver) csky*-*linux* 
    

  • The Windows native target now supports target async.

  • Floating-point support has now been added on LoongArch GNU/Linux.

  • New commands:

    * set print nibbles [on|off]
    * show print nibbles
    
    * This controls whether the 'print/t' command will display binary values in groups of four bits, known as 'nibbles'. The default is 'off'.
      Various styling-related commands. See the gdb/NEWS file for more details.
      Various maintenance commands. These are normally aimed at GDB experts or developers. See the gdb/NEWS file for more details. 
    

  • Python API improvements:

      * New Python API for instruction disassembly.
    
      * The new attribute 'locations' of gdb.Breakpoint returns a list of gdb.BreakpointLocation objects specifying the locations where the breakpoint is inserted into the debuggee.
      * New Python type gdb.BreakpointLocation.
      * New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE) that formats ADDRESS as 'address '
      * New function gdb.current_language that returns the name of the current language. Unlike gdb.parameter('language'), this will never return 'auto'.
      * New function gdb.print_options that returns a dictionary of the prevailing print options, in the form accepted by gdb.Value.format_string.
      * New method gdb.Frame.language that returns the name of the frame's language.
      * gdb.Value.format_string now uses the format provided by 'print', if it is called during a 'print' or other similar operation.
      * gdb.Value.format_string now accepts the 'summary' keyword. This can be used to request a shorter representation of a value, the way that 'set print frame-arguments scalars' does.
      * The gdb.register_window_type method now restricts the set of acceptable window names. The first character of a window's name must start with a character in the set [a-zA-Z], every subsequent character of a window's name must be in the set [-_.a-zA-Z0-9]. 
    

  • GDB/MI changes:

     * MI version 1 is deprecated, and will be removed in GDB 14.
     * The async record stating the stopped reason 'breakpoint-hit' now contains an optional field locno. 
    

  • Miscellaneous improvements:

     * gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for ELF.
     * New convenience variable $_inferior_thread_count contains the number of live threads in the current inferior.
     * New convenience variables $_hit_bpnum and $_hit_locno, set to the breakpoint number and the breakpoint location number of the breakpoint last hit.
     * The 'info breakpoints' now displays enabled breakpoint locations of disabled breakpoints as in the 'y-' state.
     * The format of 'disassemble /r' and 'record instruction-history /r' has changed to match the layout of GNU objdump when disassembling.
    
     * A new format '/b' has been introduce to provide the old behavior of '/r'.
     * The TUI no longer styles the source and assembly code highlighted by the current position indicator by default. You can however re-enable styling using the new 'set style tui-current-position' command.
     * It is now possible to use the 'document' command to document user-defined commands.
     * Support for memory tag data for AArch64 MTE. 
    

  *…

USN-4336-1 fixed several vulnerabilities in GNU binutils. This update provides the corresponding update for Ubuntu 16.04 ESM.

Original advisory details:

It was discovered that GNU binutils contained a large number of security issues. If a user or automated system were tricked into processing a specially-crafted file, a remote attacker could cause GNU binutils to crash, resulting in a denial of service, or possibly execute arbitrary code.