https://sourceware.org/bugzilla/show_bug.cgi?id=34827

            Bug ID: 34827
           Summary: GNU ld MSP430 branch expansion reads past the section
                    end
           Product: binutils
           Version: 2.46
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: basavesh.shivakumar at wsu dot edu
  Target Milestone: ---

Created attachment 17147
  --> https://sourceware.org/bugzilla/attachment.cgi?id=17147&action=edit
repro

I'm reporting this bug on behalf of my team: Ananta Srikar Puranam, Emily West,
Dr. Swarn Priya, Dr. Peng Gao and Dr. Basavesh Ammanaghatta Shivakumar.


Summary
=======

GNU ld --relax on the included MSP430 relocatable object, with
R_MSP430_10_PCREL at offset 0x803 in a 0x804-byte .text, reaches the
out-of-range branch expansion and performs a two-byte opcode load starting at
the final section byte at bfd/elf32-msp430.c:2167; the tested current ASan
build reproduces twice, GNU ld 2.46 Memcheck confirms the read, and the
offset-0x802 control is clean.

Reproduction
============

1. Download and extract
`bfd-msp430-relax-expansion-end-oob-read-reproducer.tar.gz`.
2. Run the following command with an ld.bfd or all-target `ld-new` binary that
   supports the emulation used by the reproducer:

       LD=/path/to/ld-new sh repro.sh

The archive contains the fixed input files, independent controls, helper
scripts needed by `repro.sh`, and their checksums. The script uses a temporary
directory and does not modify the source tree.

Observed result
===============

GNU ld --relax on the included MSP430 relocatable object, with
R_MSP430_10_PCREL at offset 0x803 in a 0x804-byte .text, reaches the
out-of-range branch expansion and performs a two-byte opcode load starting at
the final section byte at bfd/elf32-msp430.c:2167; the tested current ASan
build reproduces twice, GNU ld 2.46 Memcheck confirms the read, and the
offset-0x802 control is clean.

Expected result
===============

GNU ld should either produce the correct output or reject the input with a
normal diagnostic. It should not crash, hang, execute undefined behavior, read
outside an input-derived allocation, or produce the described malformed
output.

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

Reply via email to