cve.bz

CVE-2026-19548 redhat: Use After Free

5.5 mediumEPSS 0.2%Fix available

Medium (5.5) in redhat. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-19548 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-19548?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-19548?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-19548 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-19548

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-19548](https://cve.bz/cve/badge/CVE-2026-19548.svg)](https://cve.bz/cve/CVE-2026-19548)

HTML:

<a href="https://cve.bz/cve/CVE-2026-19548"><img src="https://cve.bz/cve/badge/CVE-2026-19548.svg" alt="CVE-2026-19548"></a>

Affected

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat Hardened Images2.46.1-1.4.hum1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14binutilsno fix listedDEBIAN-CVE-2026-19548
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 5 morebinutilsno fix listedUBUNTU-CVE-2026-19548
Red Hathummingbird:1binutils, binutils-gold, binutils-devel and 1 more0:2.46.1-1.4.hum1RHSA-2026:82359
openSUSETumbleweedbinutils2.47-2.1openSUSE-SU-2026:12315-1
Azure Linux3binutilsno fix listedAZL-95892

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This Moderate severity use-after-free flaw in binutils affects Red Hat products where the GNU linker is used with Link-Time Optimization (LTO) plugins enabled, such as in development and CI/CD environments. Exploitation requires an attacker to introduce a specially crafted object or archive file into the build process, leading primarily to a denial of service due to a linker crash. Arbitrary code execution is theoretically possible but significantly hindered by existing system hardening measures.

Red Hat's mitigation

Build environments should avoid running LTO-enabled linking (ld with plugin support) against untrusted or externally-supplied object and archive files. The linker is a build-time tool, not present in production runtimes, so the realistic exposure is to CI/CD pipelines and developer workstations that build from untrusted or externally-contributed sources (supply-chain style attack). Standard hardening measures (ASLR, stack protector, FORTIFY_SOURCE, PIE) substantially reduce the likelihood of arbitrary code execution via heap manipulation, limiting the more realistic impact to a linker crash (denial of service).

ProductPackageStateAdvisory
Red Hat Hardened Imagesbinutils-main-2.46.1-1.4.hum1Fixed 2026-10-13RHSA-2026:82359
Red Hat Enterprise Linux 10binutilsFix deferred
Red Hat Enterprise Linux 10gcc-toolset-15-binutilsFix deferred
Red Hat Enterprise Linux 10gcc-toolset-16-binutilsFix deferred
Red Hat Enterprise Linux 10mingw-binutilsFix deferred
Red Hat Enterprise Linux 6binutilsOut of support scope
Red Hat Enterprise Linux 7binutilsFix deferred
Red Hat Enterprise Linux 8binutilsFix deferred
Red Hat Enterprise Linux 8gcc-toolset-14-binutilsFix deferred
Red Hat Enterprise Linux 8gcc-toolset-15-binutilsFix deferred
Red Hat Enterprise Linux 8mingw-binutilsFix deferred
Red Hat Enterprise Linux 9binutilsFix deferred
Red Hat Enterprise Linux 9gcc-toolset-14-binutilsFix deferred
Red Hat Enterprise Linux 9gcc-toolset-15-binutilsFix deferred
Red Hat Enterprise Linux 9gcc-toolset-16-binutilsFix deferred
Red Hat Enterprise Linux 9mingw-binutilsFix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-dashboard-rhel9Under investigation
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-19548.

References

Check your stackJSON