Landing: c82a7005c76d
Project / Subsystem
binutils / bfd/coff
Date
2026-09-13
Author
Alan Modra <amodra@sourceware.org>
Commit
c82a7005c76d3091b62bead4f060d2be63bab5b5
Source
public_inbox
Perf win
No
Breaking
No
All attributes
- project
- binutils
- subsystem
- bfd/coff
- patch_id
- —
- commit_hash
- c82a7005c76d3091b62bead4f060d2be63bab5b5
- source_type
- public_inbox
- headline
- Fix buffer overflow in ECOFF section writing that mirrors COFF hardening.
- tldr
- ECOFF's section-write path gets the same anti-fuzzer bounds checks already applied to COFF, closing a buffer overflow.
- author
- Alan Modra <amodra@sourceware.org>
- outcome
- committed
- performance_win
- false
- breaking_change
- false
- series_id
- —
- series_parts
- []
- tags
-
- • security
- • coff
- • ecoff
- • fuzzing
- • buffer-overflow
- discussion_id_link
- public_inbox:binutils#29482
- bugzilla_pr
- —
- date
- 2026-09-13T00:00:00.000Z
The ECOFF back-end’s _bfd_ecoff_set_section_contents function lacked the sanity checks already present in the COFF equivalent, leaving a buffer-overflow vector exposed to malformed input. Alan Modra unified the guards by rewriting COFF’s check to avoid run-time division and applying the same logic to ECOFF. Fuzzers routinely craft sections with absurd sizes or offsets to trip linkers and disassemblers, so this tightening prevents crashes or security issues during object-file write operations. The fix references commit ef186fe54aa6, which introduced COFF’s original defenses, and closes PR 29482.