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

            Bug ID: 34838
           Summary: GNU ld PPC64 TLSLD relocation in a non-allocated
                    section dereferences a NULL GOT owner
           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 17158
  --> https://sourceware.org/bugzilla/attachment.cgi?id=17158&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
=======

A clean PPC64 object with a locally bound TLSLD GOT relocation in a
non-allocated section skips GOT reference counting, then dereferences the NULL
owner of the zero-initialized per-object TLSLD entry at elf64-ppc.c:16991;
current plain and GNU ld 2.46 SIGSEGV, while exact one-byte section-flag and
relocation-type controls link.

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

1. Download and extract
`bfd-ppc64-nonalloc-tlsld-null-owner-dereference-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:

       BFD=/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
===============

A clean PPC64 object with a locally bound TLSLD GOT relocation in a
non-allocated section skips GOT reference counting, then dereferences the NULL
owner of the zero-initialized per-object TLSLD entry at elf64-ppc.c:16991;
current plain and GNU ld 2.46 SIGSEGV, while exact one-byte section-flag and
relocation-type controls link.

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