[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/17512] libbfd/binutils: crashes on fuzzed samples

From: cvs-commit at gcc dot gnu.org
Subject: [Bug binutils/17512] libbfd/binutils: crashes on fuzzed samples
Date: Thu, 08 Jan 2015 15:41:31 +0000


--- Comment #162 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  063bb0250defafcc55544474a2961ecbc153882e (commit)
      from  848cde35d61874521ad6c88a50f983d5ee7d2307 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------

commit 063bb0250defafcc55544474a2961ecbc153882e
Author: Nick Clifton <address@hidden>
Date:   Thu Jan 8 15:39:49 2015 +0000

    Fix memory access violations exposed by running strip on fuzzed binaries.

        PR binutils/17512
        * coffcode.h (coff_slurp_symbol_table): Return false if we failed
        to load the line table.
        * elf.c (_bfd_elf_map_sections_to_segments): Enforce a minimum
        maxpagesize of 1.
        * peXXigen.c (_bfd_XX_bfd_copy_private_bfd_data_common): Fail if
        the Data Directory Size is too large.

        * objcopy.c (copy_object): Free the symbol table if no symbols
        could be loaded.
        (copy_file): Use bfd_close_all_done to close files that could not
        be copied.


Summary of changes:
 bfd/ChangeLog      |   10 ++++++++++
 bfd/coffcode.h     |    7 ++++---
 bfd/elf.c          |    5 +++++
 bfd/peXXigen.c     |   10 ++++++++++
 binutils/ChangeLog |    5 +++++
 binutils/objcopy.c |   14 +++++++++++++-
 6 files changed, 47 insertions(+), 4 deletions(-)

You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]