Binutils 2.39 ((TOP)) Download

The binutils have been ported to most major Unix variants as well as Wintel systems, and their main reason for existence is to give the GNU system (and GNU/Linux) the facility to compile and link programs.

Releases are made from branches in the repository, and commits are often made to the branches even after the release has gone out. The branches are named binutils-M_NN-branch where M is the major component of the version number and NN is the minor component. So the 2.41 release for example was taken from a branch called binutils-2_41-branch.

Binutils 2.39 Download

DOWNLOAD 🔥 https://urlin.us/2y2EfG 🔥

Releases and branches are tagged as well. The point where a branch was created is tagged as binutils-M_NN-branchpoint and the point where a release was created is tagged as binutils-M_NN. So for example the 2.40 release branch was split from the master branch at the binutils-2_40-branchpoint tag and the 2.40 release was made from that release at the binutils-2_40 tag.

Due to an unfortunate mistake the tag for the 2.41 release was not set to the correct location. Since this mistake was only discovered after the release had gone out we decided not to move the tag, but instead create a new one. Hence for the 2.41 release only, the release tag is called binutils-2_41-official-release.

This update for binutils fixes the following issues:

The following security bugs were fixed:

CVE-2019-1010204: Fixed out-of-bounds read in elfcpp/elfcpp_file.h (bsc#1142579).CVE-2021-3530: Fixed stack-based buffer overflow in demangle_path() in rust-demangle.c (bsc#1185597).CVE-2021-3648: Fixed infinite loop while demangling rust symbols (bsc#1188374).CVE-2021-3826: Fixed heap/stack buffer overflow in the dlang_lname function in d-demangle.c (bsc#1202969).CVE-2021-45078: Fixed out-of-bounds write in stab_xcoff_builtin_type() in stabs.c (bsc#1193929).CVE-2021-46195: Fixed uncontrolled recursion in libiberty/rust-demangle.c (bsc#1194783).CVE-2022-27943: Fixed stack exhaustion in demangle_const in (bsc#1197592).CVE-2022-38126: Fixed assertion fail in the display_debug_names() function in binutils/dwarf.c (bsc#1202966).CVE-2022-38127: Fixed NULL pointer dereference in the read_and_display_attr_value() function in binutils/dwarf.c (bsc#1202967).CVE-2022-38533: Fixed heap out-of-bounds read in bfd_getl32 (bsc#1202816).

The following non-security bugs were fixed:

SLE toolchain update of binutils, update to 2.39 from 2.37.Update to 2.39: * The ELF linker will now generate a warning message if the stack is made executable. Similarly it will warn if the output binary contains a segment with all three of the read, write and execute permission bits set. These warnings are intended to help developers identify programs which might be vulnerable to attack via these executable memory regions. The warnings are enabled by default but can be disabled via a command line option. It is also possible to build a linker with the warnings disabled, should that be necessary. * The ELF linker now supports a --package-metadata option that allows embedding a JSON payload in accordance to the Package Metadata specification. * In linker scripts it is now possible to use TYPE= in an output section description to set the section type value. * The objdump program now supports coloured/colored syntax highlighting of its disassembler output for some architectures. (Currently: AVR, RiscV, s390, x86, x86_64). * The nm program now supports a --no-weak/-W option to make it ignore weak symbols. * The readelf and objdump programs now support a -wE option to prevent them from attempting to access debuginfod servers when following links. * The objcopy program's --weaken, --weaken-symbol, and --weaken-symbols options now works with unique symbols as well.

Update to 2.38: * elfedit: Add --output-abiversion option to update ABIVERSION. * Add support for the LoongArch instruction set. * Tools which display symbols or strings (readelf, strings, nm, objdump) have a new command line option which controls how unicode characters are handled. By default they are treated as normal for the tool. Using --unicode=locale will display them according to the current locale. Using --unicode=hex will display them as hex byte values, whilst --unicode=escape will display them as escape sequences. In addition using --unicode=highlight will display them as unicode escape sequences highlighted in red (if supported by the output device). * readelf -r dumps RELR relative relocations now. * Support for efi-app-aarch64, efi-rtdrv-aarch64 and efi-bsdrv-aarch64 has been added to objcopy in order to enable UEFI development using binutils. * ar: Add --thin for creating thin archives. -T is a deprecated alias without diagnostics. In many ar implementations -T has a different meaning, as specified by X/Open System Interface. * Add support for AArch64 system registers that were missing in previous releases. * Add support for the LoongArch instruction set. * Add a command-line option, -muse-unaligned-vector-move, for x86 target to encode aligned vector move as unaligned vector move. * Add support for Cortex-R52+ for Arm. * Add support for Cortex-A510, Cortex-A710, Cortex-X2 for AArch64. * Add support for Cortex-A710 for Arm. * Add support for Scalable Matrix Extension (SME) for AArch64. * The --multibyte-handling=[allow|warn|warn-sym-only] option tells the assembler what to when it encoutners multibyte characters in the input. The default is to allow them. Setting the option to "warn" will generate a warning message whenever any multibyte character is encountered. Using the option to "warn-sym-only" will make the assembler generate a warning whenever a symbol is defined containing multibyte characters. (References to undefined symbols will not generate warnings). * Outputs of .ds.x directive and .tfloat directive with hex input from x86 assembler have been reduced from 12 bytes to 10 bytes to match the output of .tfloat directive. * Add support for 'armv8.8-a', 'armv9-a', 'armv9.1-a', 'armv9.2-a' and 'armv9.3-a' for -march in AArch64 GAS. * Add support for 'armv8.7-a', 'armv8.8-a', 'armv9-a', 'armv9.1-a', 'armv9.2-a' and 'armv9.3-a' for -march in Arm GAS. * Add support for Intel AVX512_FP16 instructions. * Add -z pack-relative-relocs/-z no pack-relative-relocs to x86 ELF linker to pack relative relocations in the DT_RELR section. * Add support for the LoongArch architecture. * Add -z indirect-extern-access/-z noindirect-extern-access to x86 ELF linker to control canonical function pointers and copy relocation. * Add --max-cache-size=SIZE to set the the maximum cache size to SIZE bytes.Explicitly enable --enable-warn-execstack=yes and --enable-warn-rwx-segments=yes.Add gprofng subpackage.Include recognition of 'z16' name for 'arch14' on s390. (bsc#1198237).Add back fix for bsc#1191473, which got lost in the update to 2.38.Install symlinks for all target specific tools on arm-eabi-none (bsc#1185712).Enable PRU architecture for AM335x CPU (Beagle Bone Black board)

It was discovered that GNU binutils incorrectly handled certain DWARF

files. An attacker could possibly use this issue to cause a crash or

execute arbitrary code. This issue only affected Ubuntu 22.10.

(CVE-2023-1579)

It was discovered that GNU binutils did not properly verify the version

definitions in zer0-lengthverdef table. An attacker could possibly use this

issue to cause a crash or execute arbitrary code. This issue only affected

Ubuntu 22.04 LTS, Ubuntu 22.10 and Ubuntu 23.04. (CVE-2023-1972)

It was discovered that GNU binutils did not properly validate the size of

length parameter in vms-alpha. An attacker could possibly use this issue to

cause a crash or access sensitive information. This issue only affected

Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, Ubuntu 22.04 LTS and Ubuntu 22.10.

(CVE-2023-25584)

It was discovered that GNU binutils did not properly initialized the

file_table field of struct module and the_bfd field of asymbol. An attacker

could possibly use this issue to cause a crash. This issue only affected

Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, Ubuntu 20.04 LTS and

Ubuntu 22.04 LTS. (CVE-2023-25585, CVE-2023-25588)

Hi Heitbaum, could you tell me which toolchain you're using to build TF-A? The latest Arm GNU AArch64 toolchain is 11.3.Rel1, which packages binutils-2.38 and therefore compiles successfully, so I'm currently unable to reproduce this error.

I can confirm this occurs with binutils 2.39. We (coreboot) are trying to update binutils from our toolchain and we are about to adjust our build system. --no-warn-rwx-segment fixes the issue. +/66920

The GNU Binutils version 2.39 was released before Fedora 38; and we have already been using this version of binutils in Fedora Rawhide successfully to build the distribution for the last 4 months. Given the present schedule for Fedora 38 we will continue to use Binutils 2.39.

The GNU Binutils has its own testsuite which is run during the package build and examined by binutils developers before being uploaded. The regression testsuite is run to verify the correct operation of the static linker and attendant utilities. ff782bc1db