Issue 372093895: binutils:fuzz_dlltool: Null-dereference READ in _bfd_mips_elf_symbol_processing

[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/372093895

Reference Info: 372093895 binutils:fuzz_dlltool: Null-dereference READ in _bfd_mips_elf_symbol_processing

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:  Bug
access level:  Limited visibility
priority:  P2
severity:  S4
hotlist:  Reproducible, Stability-Memory-AddressSanitizer
retention:  Component default
Project:  binutils
Reported:  Oct 8, 2024

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

Project: binutils
Fuzzing Engine: honggfuzz
Fuzz Target: fuzz_dlltool
Job Type: honggfuzz_asan_binutils
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  _bfd_mips_elf_symbol_processing
  bfd_elf64_slurp_symbol_table
  _bfd_elf_canonicalize_symtab
 
Sanitizer: address (ASAN)

Regressed: https://oss-fuzz.com/revisions?job=honggfuzz_asan_binutils&range=202410020612:202410030621

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

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 372093895
Unsubscribe from this issue.