<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 20:16:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-19548 — Binutils: binutils: multiple use-after-free in add_archive_element via lto plugin processing</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-19548</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat Hardened Images, Red Hat OpenShift Container Platform 4&lt;/p&gt;
&lt;p&gt;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-&amp;gt;the_bfd-&amp;gt;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:&lt;/p&gt;
&lt;p&gt;1. Line ~1442: accessing abfd-&amp;gt;my_archive via bfd_usrdata(abfd-&amp;gt;my_archive)
2. Line ~1493: multiple accesses to abfd and abfd-&amp;gt;my_archive in a conditional check and bfd_get_filename call
3. Line ~1525: dereferencing the shallow copy orig_input.the_bfd-&amp;gt;my_archive in trace/verbose logging&lt;/p&gt;
&lt;p&gt;The vulnerability is triggered when LTO plugins are active (link_info.lto_plugin_active is true) and the input object has abfd-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat Hardened Images, Red Hat OpenShift Container Platform 4&lt;/p&gt;
&lt;p&gt;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-&amp;gt;the_bfd-&amp;gt;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:&lt;/p&gt;
&lt;p&gt;1. Line ~1442: accessing abfd-&amp;gt;my_archive via bfd_usrdata(abfd-&amp;gt;my_archive)
2. Line ~1493: multiple accesses to abfd and abfd-&amp;gt;my_archive in a conditional check and bfd_get_filename call
3. Line ~1525: dereferencing the shallow copy orig_input.the_bfd-&amp;gt;my_archive in trace/verbose logging&lt;/p&gt;
&lt;p&gt;The vulnerability is triggered when LTO plugins are active (link_info.lto_plugin_active is true) and the input object has abfd-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-19548</guid>
    </item>
  </channel>
</rss>
