BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-1151High confidence

GNU Binutils ld xmemdup.c xmemdup memory leak

GNU · Binutils

2.3LowCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

Low technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 65 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityLowOperational priority:Medium, raised one band.upgradedsince 12 Feb 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 0.61% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs GNU Binutils and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 65 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcebinutilsAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcebinutilsAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcebinutilsVendor fix publishedDebian records a fixed source-package version for this release.2.45-3Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcebinutilsVendor fix publishedDebian records a fixed source-package version for this release.2.45-3Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivebinutilsUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2025-1151 · CSAF 2.0 · revision 47 · interimSUSE Product Security TeamCVE-2025-1151
141 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • binutils as component of SUSE Linux Enterprise Desktop 15 SP6
  • binutils-devel-32bit as component of SUSE Linux Enterprise Desktop 15 SP6
  • binutils as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • binutils-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • binutils as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • binutils-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • libctf-nobfd0 as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • libctf0 as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • binutils as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • binutils-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • libctf-nobfd0 as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • libctf0 as component of SUSE Linux Enterprise High Performance Computing 12 SP5
Summary
A vulnerability was found in GNU Binutils 2.43. It has been rated as problematic. This issue affects the function xmemdup of the file xmemdup.c of the component ld. The manipulation leads to memory leak. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2025-1151 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitybinutils: GNU Binutils ld xmemdup.c xmemdup memory leak
63 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • binutils as a component of Red Hat Enterprise Linux 10
  • binutils-devel as a component of Red Hat Enterprise Linux 10
  • binutils-gold as a component of Red Hat Enterprise Linux 10
  • binutils.src as a component of Red Hat Enterprise Linux 10
  • mingw-binutils-generic as a component of Red Hat Enterprise Linux 10
  • mingw32-binutils as a component of Red Hat Enterprise Linux 10
  • mingw64-binutils as a component of Red Hat Enterprise Linux 10
  • binutils-devel as a component of Red Hat Enterprise Linux 6
  • binutils.src as a component of Red Hat Enterprise Linux 6
  • binutils as a component of Red Hat Enterprise Linux 7
  • binutils-devel as a component of Red Hat Enterprise Linux 7
  • binutils.src as a component of Red Hat Enterprise Linux 7
Summary
A flaw was found in the ld linker utility of GNU Binutils. A specially-crafted payload may be able to trigger a memory leak, which can lead to an application crash or other undefined behavior.
Remediation
Fix deferred
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-2026

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Low technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 65 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

A vulnerability was found in GNU Binutils 2.43. It has been rated as problematic. This issue affects the function xmemdup of the file xmemdup.c of the component ld. The manipulation leads to memory leak. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

What

A vulnerability was found in GNU Binutils 2.43. It has been rated as problematic. This issue affects the function xmemdup of the file xmemdup.c of the component ld. The manipulation leads to memory leak. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How

An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

A vulnerability was found in GNU Binutils 2.43. It has been rated as problematic. This issue affects the function xmemdup of the file xmemdup.c of the component ld. The manipulation leads to memory leak. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How

An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Missing Release of Memory after Effective Lifetime → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Passive interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-401 ↗

CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIPassiveUser interaction: A user must unknowingly interact with the vulnerable system.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VALowVulnerable-system availability: A successful attack can cause a limited loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-401Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1730Xerox FreeFlow Print Server: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-0304binutils: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in binutils ausnutzen, um einen Denial of Service-Zustand zu erzeugen oder nicht spezifizierte Auswirkungen zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250213Security Bulletin 13 February 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 13 February 2025, published on 13 February 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

ERecord?id=CVE-2025-10158 Référence CVE CVE-2025-10911 https://www.cve.org/CVERecord?id=CVE-2025-10911 Référence CVE CVE-2025-11065 https://www.cve.org/CVERecord?id=CVE-2025-11065 Référence CVE CVE-2025-1118 https://www.cve.org/CVERecord?id=CVE-2025-1118 Référence CVE CVE-2025-11187 https://www.cve.org/CVERecord?id=CVE-2025-11187 Référence CVE CVE-2025-11226 https://www.cve.org/CVERecord?id=CVE-2025-11226 Référence CVE CVE-2025-11234 https://www.cve.org/CVERecord?id=CVE-2025-11234 Référence CVE CVE-2025-1125 https://www.cve.org/CVERecord?id=CVE-2025-1125 Référence CVE CVE-2025-1150 https://www.cve.org/CVERecord?id=CVE-2025-1150 Référence CVE CVE-2025-1151 https://www.cve.org/CVERecord?id=CVE-2025-1151 Référence CVE CVE-2025-1152 https://www.cve.org/CVERecord?id=CVE-2025-1152 Référence CVE CVE-2025-11731 https://www.cve.org/CVERecord?id=CVE-2025-11731 Référence CVE CVE-2025-1180 https://www.cve.org/CVERecord?id=CVE-2025-1180 Référence CVE CVE-2025-11961 https://www.cve.org/CVERecord?id=CVE-2025-11961 Référence CVE CVE-2025-12084 https://www.cve.org/CVERecord?id=CVE-2025-12084 Référence CVE CVE-2025-1272 https://www.cve.org/CVERecord?id=CVE-2025-1272 Référence CVE CVE-2025-12801 https://www.cve.org/CVERecord?id=CVE-2025-12801 Référence CVE CVE-2025-13462 https://www.cve.org/CVERecord?id=CVE-202

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

VERecord?id=CVE-2025-0913 Référence CVE CVE-2025-10158 https://www.cve.org/CVERecord?id=CVE-2025-10158 Référence CVE CVE-2025-10911 https://www.cve.org/CVERecord?id=CVE-2025-10911 Référence CVE CVE-2025-11065 https://www.cve.org/CVERecord?id=CVE-2025-11065 Référence CVE CVE-2025-1118 https://www.cve.org/CVERecord?id=CVE-2025-1118 Référence CVE CVE-2025-11187 https://www.cve.org/CVERecord?id=CVE-2025-11187 Référence CVE CVE-2025-11234 https://www.cve.org/CVERecord?id=CVE-2025-11234 Référence CVE CVE-2025-1125 https://www.cve.org/CVERecord?id=CVE-2025-1125 Référence CVE CVE-2025-1150 https://www.cve.org/CVERecord?id=CVE-2025-1150 Référence CVE CVE-2025-1151 https://www.cve.org/CVERecord?id=CVE-2025-1151 Référence CVE CVE-2025-1152 https://www.cve.org/CVERecord?id=CVE-2025-1152 Référence CVE CVE-2025-11731 https://www.cve.org/CVERecord?id=CVE-2025-11731 Référence CVE CVE-2025-1180 https://www.cve.org/CVERecord?id=CVE-2025-1180 Référence CVE CVE-2025-11961 https://www.cve.org/CVERecord?id=CVE-2025-11961 Référence CVE CVE-2025-1272 https://www.cve.org/CVERecord?id=CVE-2025-1272 Référence CVE CVE-2025-12801 https://www.cve.org/CVERecord?id=CVE-2025-12801 Référence CVE CVE-2025-13462 https://www.cve.org/CVERecord?id=CVE-2025-13462 Référence CVE CVE-2025-1352 https://www.cve.org/CVERecord?id=CVE-2025

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0218Multiples vulnérabilités dans les produits VMware

ERecord?id=CVE-2025-11083 Référence CVE CVE-2025-11412 https://www.cve.org/CVERecord?id=CVE-2025-11412 Référence CVE CVE-2025-11414 https://www.cve.org/CVERecord?id=CVE-2025-11414 Référence CVE CVE-2025-11468 https://www.cve.org/CVERecord?id=CVE-2025-11468 Référence CVE CVE-2025-1148 https://www.cve.org/CVERecord?id=CVE-2025-1148 Référence CVE CVE-2025-1149 https://www.cve.org/CVERecord?id=CVE-2025-1149 Référence CVE CVE-2025-11494 https://www.cve.org/CVERecord?id=CVE-2025-11494 Référence CVE CVE-2025-11495 https://www.cve.org/CVERecord?id=CVE-2025-11495 Référence CVE CVE-2025-1150 https://www.cve.org/CVERecord?id=CVE-2025-1150 Référence CVE CVE-2025-1151 https://www.cve.org/CVERecord?id=CVE-2025-1151 Référence CVE CVE-2025-1152 https://www.cve.org/CVERecord?id=CVE-2025-1152 Référence CVE CVE-2025-1153 https://www.cve.org/CVERecord?id=CVE-2025-1153 Référence CVE CVE-2025-11731 https://www.cve.org/CVERecord?id=CVE-2025-11731 Référence CVE CVE-2025-1176 https://www.cve.org/CVERecord?id=CVE-2025-1176 Référence CVE CVE-2025-1178 https://www.cve.org/CVERecord?id=CVE-2025-1178 Référence CVE CVE-2025-1179 https://www.cve.org/CVERecord?id=CVE-2025-1179 Référence CVE CVE-2025-1180 https://www.cve.org/CVERecord?id=CVE-2025-1180 Référence CVE CVE-2025-1181 https://www.cve.org/CVERecord?id=CVE-2025-1181

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0693Multiples vulnérabilités dans VMware Tanzu

e.org/CVERecord?id=CVE-2024-56171 Référence CVE CVE-2024-57360 https://www.cve.org/CVERecord?id=CVE-2024-57360 Référence CVE CVE-2024-7592 https://www.cve.org/CVERecord?id=CVE-2024-7592 Référence CVE CVE-2024-8176 https://www.cve.org/CVERecord?id=CVE-2024-8176 Référence CVE CVE-2024-9287 https://www.cve.org/CVERecord?id=CVE-2024-9287 Référence CVE CVE-2025-0395 https://www.cve.org/CVERecord?id=CVE-2025-0395 Référence CVE CVE-2025-0913 https://www.cve.org/CVERecord?id=CVE-2025-0913 Référence CVE CVE-2025-0938 https://www.cve.org/CVERecord?id=CVE-2025-0938 Référence CVE CVE-2025-1150 https://www.cve.org/CVERecord?id=CVE-2025-1150 Référence CVE CVE-2025-1151 https://www.cve.org/CVERecord?id=CVE-2025-1151 Référence CVE CVE-2025-1152 https://www.cve.org/CVERecord?id=CVE-2025-1152 Référence CVE CVE-2025-1153 https://www.cve.org/CVERecord?id=CVE-2025-1153 Référence CVE CVE-2025-1215 https://www.cve.org/CVERecord?id=CVE-2025-1215 Référence CVE CVE-2025-1371 https://www.cve.org/CVERecord?id=CVE-2025-1371 Référence CVE CVE-2025-1376 https://www.cve.org/CVERecord?id=CVE-2025-1376 Référence CVE CVE-2025-1377 https://www.cve.org/CVERecord?id=CVE-2025-1377 Référence CVE CVE-2025-1795 https://www.cve.org/CVERecord?id=CVE-2025-1795 Référence CVE CVE-2025-22134 https://www.cve.org/CVERecord?id=CVE-2025-22134

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-001958GNU Project の GNU Binutils における有効期限後のメモリの解放の欠如に関する脆弱性

GNU Project の GNU Binutils には、有効期限後のメモリの解放の欠如に関する脆弱性、リソースの不適切なシャットダウンおよびリリースに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 10 Feb 2025 · Last source change 12 Feb 2025, 15:47 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-2026
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    SUSE Product Security Team ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    binutils as a component of Red Hat Enterprise Linux 10; binutils-devel as a component of Red Hat Enterprise Linux 10; binutils-gold as a component of Red Hat Enterprise Linux 10; binutils.src as a component of Red Hat Enterprise Linux 10; mingw-binutils-generic as a component of Red Hat Enterprise Linux 10; mingw32-binutils as a component of Red Hat Enterprise Linux 10; mingw64-binutils as a component of Red Hat Enterprise Linux 10; binutils-devel as a component of Red Hat Enterprise Linux 6; binutils.src as a component of Red Hat Enterprise Linux 6; binutils as a component of Red Hat Enterprise Linux 7; binutils-devel as a component of Red Hat Enterprise Linux 7; binutils.src as a component of Red Hat Enterprise Linux 7; gdb-doc as a component of Red Hat Enterprise Linux 7; gdb-gdbserver as a component of Red Hat Enterprise Linux 7; gdb.src as a component of Red Hat Enterprise Linux 7; binutils as a component of Red Hat Enterprise Linux 8; binutils-devel as a component of Red Hat Enterprise Linux 8; binutils.src as a component of Red Hat Enterprise Linux 8; gcc-toolset-13-binutils-devel as a component of Red Hat Enterprise Linux 8; gcc-toolset-13-binutils-gold as a component of Red Hat Enterprise Linux 8; gcc-toolset-13-binutils.src as a component of Red Hat Enterprise Linux 8; gcc-toolset-13-gdb.src as a component of Red Hat Enterprise Linux 8; gcc-toolset-14-binutils as a component of Red Hat Enterprise Linux 8; gcc-toolset-14-binutils-devel as a component of Red Hat Enterprise Linux 8; gcc-toolset-14-binutils-gold as a component of Red Hat Enterprise Linux 8; gcc-toolset-14-binutils-gprofng as a component of Red Hat Enterprise Linux 8; gcc-toolset-14-binutils.src as a component of Red Hat Enterprise Linux 8; gcc-toolset-14-gdb.src as a component of Red Hat Enterprise Linux 8; gdb as a component of Red Hat Enterprise Linux 8; gdb-doc as a component of Red Hat Enterprise Linux 8; and 32 more
    After
    binutils as a component of Red Hat Enterprise Linux 10; binutils-devel as a component of Red Hat Enterprise Linux 10; binutils-gold as a component of Red Hat Enterprise Linux 10; binutils.src as a component of Red Hat Enterprise Linux 10; mingw-binutils-generic as a component of Red Hat Enterprise Linux 10; mingw32-binutils as a component of Red Hat Enterprise Linux 10; mingw64-binutils as a component of Red Hat Enterprise Linux 10; binutils-devel as a component of Red Hat Enterprise Linux 6; binutils.src as a component of Red Hat Enterprise Linux 6; binutils as a component of Red Hat Enterprise Linux 7; binutils-devel as a component of Red Hat Enterprise Linux 7; binutils.src as a component of Red Hat Enterprise Linux 7; gdb-doc as a component of Red Hat Enterprise Linux 7; gdb-gdbserver as a component of Red Hat Enterprise Linux 7; gdb.src as a component of Red Hat Enterprise Linux 7; binutils as a component of Red Hat Enterprise Linux 8; binutils-devel as a component of Red Hat Enterprise Linux 8; binutils.src as a component of Red Hat Enterprise Linux 8; gcc-toolset-13-binutils-devel as a component of Red Hat Enterprise Linux 8; gcc-toolset-13-binutils-gold as a component of Red Hat Enterprise Linux 8; gcc-toolset-13-binutils.src as a component of Red Hat Enterprise Linux 8; gcc-toolset-13-gdb.src as a component of Red Hat Enterprise Linux 8; gcc-toolset-14-binutils as a component of Red Hat Enterprise Linux 8; gcc-toolset-14-binutils-devel as a component of Red Hat Enterprise Linux 8; gcc-toolset-14-binutils-gold as a component of Red Hat Enterprise Linux 8; gcc-toolset-14-binutils-gprofng as a component of Red Hat Enterprise Linux 8; gcc-toolset-14-binutils.src as a component of Red Hat Enterprise Linux 8; gcc-toolset-14-gdb.src as a component of Red Hat Enterprise Linux 8; gdb as a component of Red Hat Enterprise Linux 8; gdb-doc as a component of Red Hat Enterprise Linux 8; and 33 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-1151 · cve.blacktree.nl