Issue 390467759: binutils:fuzz_objcopy: Heap-double-free in fuzz_objcopy.c

[buganizer-system]

Replying to this email means your email address will be shared with the team that works on this product.

https://issues.oss-fuzz.com/issues/390467759

Reference Info: 390467759 binutils:fuzz_objcopy: Heap-double-free in fuzz_objcopy.c

component:  Public Trackers > 1362134 > OSS Fuzz
status:  New
reporter:  87...@developer.gserviceaccount.com
cc:  am...@gmail.com, bug-binutils@gnu.org, da...@adalogics.com, and 2 more
collaborators:  co...@oss-fuzz.com
type:  Vulnerability
access level:  Limited visibility
priority:  P2
severity:  S1
hotlist:  Reproducible, Stability-LibFuzzer, Stability-Memory-AddressSanitizer
retention:  Component default
Project:  binutils
Reported:  Jan 17, 2025

87...@developer.gserviceaccount.com added comment #1:
Detailed Report: https://oss-fuzz.com/testcase?key=6614335023022080

Project: binutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz_objcopy
Job Type: libfuzzer_asan_binutils
Platform Id: linux

Crash Type: Heap-double-free
Crash Address: 0x5020000000d0
Crash State:
  fuzz_objcopy.c
  tekhex_write_object_contents
  bfd_close
 
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_binutils&range=202501160649:202501170634

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6614335023022080

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.
When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any stable releases.
  * add any other useful information.
This information can help downstream consumers.

If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored.

This bug is subject to a 90 day disclosure deadline. If 90 days elapse
without an upstream patch, then the bug report will automatically
become visible to the public.


Generated by Google IssueTracker notification system.

You're receiving this email because you are subscribed to updates on Google IssueTracker issue 390467759
Unsubscribe from this issue.