https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 03:55:08 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-19548 <p>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-&gt;the_bfd-&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:</p> <p>1. Line ~1442: accessing abfd-&gt;my_archive via bfd_usrdata(abfd-&gt;my_archive) 2. Line ~1493: multiple accesses to abfd and abfd-&gt;my_archive in a conditional check and bfd_get_filename call 3. Line ~1525: dereferencing the shallow copy orig_input.the_bfd-&gt;my_archive in trace/verbose logging</p> <p>The vulnerability is triggered when LTO plugins are active (link_info.lto_plugin_active is true) and the input object has abfd-&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.</p> <p>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…</p> <p>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-&gt;the_bfd-&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:</p> <p>1. Line ~1442: accessing abfd-&gt;my_archive via bfd_usrdata(abfd-&gt;my_archive) 2. Line ~1493: multiple accesses to abfd and abfd-&gt;my_archive in a conditional check and bfd_get_filename call 3. Line ~1525: dereferencing the shallow copy orig_input.the_bfd-&gt;my_archive in trace/verbose logging</p> <p>The vulnerability is triggered when LTO plugins are active (link_info.lto_plugin_active is true) and the input object has abfd-&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.</p> <p>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…</p> https://db.gcve.eu/vuln/fkie_cve-2026-19548 https://db.gcve.eu/vuln/ghsa-j77f-3ffj-4jg4 <p>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-&gt;the_bfd-&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:</p> <p>1. Line ~1442: accessing abfd-&gt;my_archive via bfd_usrdata(abfd-&gt;my_archive) 2. Line ~1493: multiple accesses to abfd and abfd-&gt;my_archive in a conditional check and bfd_get_filename call 3. Line ~1525: dereferencing the shallow copy orig_input.the_bfd-&gt;my_archive in trace/verbose logging</p> <p>The vulnerability is triggered when LTO plugins are active (link_info.lto_plugin_active is true) and the input object has abfd-&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.</p> <p>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…</p> <p>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-&gt;the_bfd-&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:</p> <p>1. Line ~1442: accessing abfd-&gt;my_archive via bfd_usrdata(abfd-&gt;my_archive) 2. Line ~1493: multiple accesses to abfd and abfd-&gt;my_archive in a conditional check and bfd_get_filename call 3. Line ~1525: dereferencing the shallow copy orig_input.the_bfd-&gt;my_archive in trace/verbose logging</p> <p>The vulnerability is triggered when LTO plugins are active (link_info.lto_plugin_active is true) and the input object has abfd-&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.</p> <p>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…</p> https://db.gcve.eu/vuln/ghsa-j77f-3ffj-4jg4 https://db.gcve.eu/vuln/msrc_cve-2026-19548 msrc_CVE-2026-19548 https://db.gcve.eu/vuln/msrc_cve-2026-19548 https://db.gcve.eu/vuln/ubuntu-cve-2026-19548 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: binutils, Ubuntu:Pro:16.04:LTS: binutils, Ubuntu:Pro:18.04:LTS: binutils, Ubuntu:Pro:20.04:LTS: binutils, Ubuntu:22.04:LTS: binutils, Ubuntu:24.04:LTS: binutils, Ubuntu:26.04:LTS: binutils</p> <p>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-&gt;the_bfd-&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: 1. Line ~1442: accessing abfd-&gt;my_archive via bfd_usrdata(abfd-&gt;my_archive) 2. Line ~1493: multiple accesses to abfd and abfd-&gt;my_archive in a conditional check and bfd_get_filename call 3. Line ~1525: dereferencing the shallow copy orig_input.the_bfd-&gt;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-&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. 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 pr…</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: binutils, Ubuntu:Pro:16.04:LTS: binutils, Ubuntu:Pro:18.04:LTS: binutils, Ubuntu:Pro:20.04:LTS: binutils, Ubuntu:22.04:LTS: binutils, Ubuntu:24.04:LTS: binutils, Ubuntu:26.04:LTS: binutils</p> <p>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-&gt;the_bfd-&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: 1. Line ~1442: accessing abfd-&gt;my_archive via bfd_usrdata(abfd-&gt;my_archive) 2. Line ~1493: multiple accesses to abfd and abfd-&gt;my_archive in a conditional check and bfd_get_filename call 3. Line ~1525: dereferencing the shallow copy orig_input.the_bfd-&gt;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-&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. 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 pr…</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-19548