VYPR
← All advisories
Unrated severityNVD Advisory· Published Feb 11, 2025· Updated Feb 11, 2025

GNU Binutils ld libbfd.c bfd_putl64 memory corruption

CVE-2025-1179

Description

A critical memory corruption vulnerability in GNU Binutils 2.43's ld component via bfd_putl64, requiring high attack complexity.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A critical memory corruption vulnerability in GNU Binutils 2.43's ld component via bfd_putl64, requiring high attack complexity.

Vulnerability

A critical memory corruption vulnerability exists in GNU Binutils version 2.43. The flaw is located in the bfd_putl64 function within the file bfd/libbfd.c of the ld component [1]. The vulnerability is triggered during specific manipulation, leading to memory corruption. The affected version is 2.43; the issue has been fixed in version 2.44 [1].

Exploitation

The attack can be launched remotely, but the complexity is high and exploitation is considered difficult [1]. An attacker would need to craft a malicious input that triggers the memory corruption through the bfd_putl64 function in the linker. Public exploit details have been disclosed, which could aid in weaponization [1].

Impact

Successful exploitation results in memory corruption, which could lead to denial of service, information disclosure, or potentially arbitrary code execution depending on the specific corruption. The attack is remotely exploitable, raising the severity to critical [1].

Mitigation

Upgrading to GNU Binutils version 2.44 is recommended to address this issue [1]. The code maintainer states that the bug was fixed between the 2.43 and 2.44 releases [1]. No workarounds have been disclosed in the available references.

References
  1. The GNU Operating System and the Free Software Movement

AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

112

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

7

News mentions

0

No linked articles in our index yet.