Linker crash via invalid TLS descriptor relocation
Published Feb 11, 2025 · Updated Feb 11, 2025
Memory corruption in GNU Binutils ld 2.43 allows attackers to crash the linker via a malformed x86 object file processed with -w. The x86 relocation path checks the required indirect-call encoding only during TLS transition, allowing an invalid TLS descriptor relocation to reach bfd_putl64. Exploitation requires the linker to process the crafted object with warnings suppressed; the demonstrated consequence is a linker crash.
Summary
What happened
Memory corruption in GNU Binutils ld 2.43 allows attackers to crash the linker via a malformed x86 object file processed with -w. The x86 relocation path checks the required indirect-call encoding only during TLS transition, allowing an invalid TLS descriptor relocation to reach bfd_putl64. Exploitation requires the linker to process the crafted object with warnings suppressed; the demonstrated consequence is a linker crash.
The record
- CVE
- CVE-2025-1179
- Published
- Feb 11, 2025
- Updated
- Feb 11, 2025
- Vendor
- The GnuPG Project
- Product
- GNU Binutils
- Classifications
- CWE-119
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2025CVE publishedPublication date reported by the CVE source.
- Feb 11, 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
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
- Malformed object-file crash proof of conceptproof of concept · demonstrated
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