Vulnerability · Published Aug 12, 2026 · Assigned by redhat

CVE-2026-19548Binutils: binutils: multiple use-after-free in add_archive_element via lto plugin processing

Medium 5.5

In plain English

A medium-severity use-after-free in Red Hat Enterprise Linux 10 from Red Hat. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities).

Severity (CVSS 3.1)5.5Medium
Exploit odds (30 days)0.2%top 93.9% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

Multiple Use-After-Free vulnerabilities were found in the add_archive_element function in ld/ldmain.c of the GNU linker (ld), a component of binutils. The root cause is that plugin_maybe_claim() in ld/plugin.c frees the original BFD object via bfd_close/_bfd_delete_bfd when entry->the_bfd->my_archive == NULL, but the caller retains both the original abfd parameter and a shallow copy (orig_input.the_bfd) as dangling pointers. These dangling pointers are subsequently dereferenced at three distinct locations in add_archive_element: 1. Line ~1442: accessing abfd->my_archive via bfd_usrdata(abfd->my_archive) 2. Line ~1493: multiple accesses to abfd and abfd->my_archive in a conditional check and bfd_get_filename call 3. Line ~1525: dereferencing the shallow copy orig_input.the_bfd->my_archive in trace/verbose logging The vulnerability is triggered when LTO plugins are active (link_info.lto_plugin_active is true) and the input object has abfd->my_archive == NULL, which is a valid state for standalone object files. Red Hat builds binutils with --enable-plugins and --enable-lto, confirming the vulnerable code path is compiled in and reachable. An attacker who can supply a crafted object or archive file to a build process using LTO-enabled linking could exploit this flaw to cause a denial of service (linker crash via segmentation fault). Arbitrary code execution is theoretically possible through heap manipulation but is substantially mitigated by hardening measures including stack protector, FORTIFY_SOURCE, ASLR, and PIE. The attack surface is limited to build-time environments — the linker is a development tool not exposed in production runtime. The most realistic exploitation scenario is a supply chain attack introducing a crafted object file as a build dependency in CI/CD pipelines or development environments.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12binutilsno fix listedDEBIAN-CVE-2026-19548
Debian:13binutilsno fix listedDEBIAN-CVE-2026-19548
Debian:14binutilsno fix listedDEBIAN-CVE-2026-19548
Ubuntu:22.04:LTSbinutilsno fix listedUBUNTU-CVE-2026-19548
Ubuntu:24.04:LTSbinutilsno fix listedUBUNTU-CVE-2026-19548
Ubuntu:26.04:LTSbinutilsno fix listedUBUNTU-CVE-2026-19548
Ubuntu:26.10binutilsno fix listedUBUNTU-CVE-2026-19548

Affected products (as reported)

Weakness: CWE-416 · Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

References