Linker crash via failed output-file setup
Published Feb 10, 2025 · Updated Apr 4, 2025
Memory corruption in bfd_set_format in GNU Binutils 2.43 and 2.44 allows attackers to crash ld via an unwritable output path. The linker reaches bfd_set_format after output-file creation fails and continues using the failed output state instead of stopping. Triggering the fault requires warning suppression, an output location that cannot be opened, and execution of ld; impact is limited to termination of that linker process.
Summary
What happened
Memory corruption in bfd_set_format in GNU Binutils 2.43 and 2.44 allows attackers to crash ld via an unwritable output path. The linker reaches bfd_set_format after output-file creation fails and continues using the failed output state instead of stopping. Triggering the fault requires warning suppression, an output location that cannot be opened, and execution of ld; impact is limited to termination of that linker process.
The record
- CVE
- CVE-2025-1153
- Published
- Feb 10, 2025
- Updated
- Apr 4, 2025
- Vendor
- The GnuPG Project
- Product
- GNU Binutils
- Classifications
- CWE-119, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 2025CVE publishedPublication date reported by the CVE source.
- Apr 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.43
- Affected versionversion=2.44
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo