[Bug demangler/106622] New: Bug report

["sophrosx at gmail dot com" <gcc-bugzilla@gcc.gnu.org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106622

            Bug ID: 106622
           Summary: Bug report
           Product: gcc
           Version: rust/master
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: demangler
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sophrosx at gmail dot com
  Target Milestone: ---

Created attachment 53459
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53459&action=edit
testcases for nm-new

Hello,

I detected the memory leak and dead loop problems through fuzz testing, which I
think might be a vulnerability.

I found that the binutils-gdb[https://github.com/bminor/binutils-gdb]'s program
nm-new with the test inputs triggered dead loop and memory leak
vulnerabilities. As a result, I submit the testcases to binutils and here is
the bug report[https://sourceware.org/bugzilla/show_bug.cgi?id=29492].

The configuration of binutils is:

$  ./configure --disable-shared && make -j

and compiled with gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0

Then the maintainer Alan Modra[amodra@gmail.com] told me that the endless
looping is all in the rust demangler. What is more, the symbols being demangled
are:
1) _RYXBAL_OFFGLOBTABLE_
2) _RYFGNUSLT_FHStNB10ay_start
3) _RYDGLOBOFFSET_TABLE_
4) _RYFGDIC6gnu_compilediBtOhighlightEH_FRAME_HDR
5) _RYFUDGC6ShigdefaulttiBtOhighlightEH_FRAME_HDR
6) _RYFUDGC6Shighdignu_compiledhlightEH_FRAME_HDR
7) _RYFIMYeB_xDGLtSarray_start
8) _RYdMMYTopFinFGAarral_start
9) _RMYADGC0hdpnit_Grray_start
10) _RYNSMICu2FiFGtDBrray_s
11) _RYTOdPjesistePDGC1onRLab_e
12) _RIYADGO0Rdpnit_Grray_start

Further more, I add those testcases in the attachment. If there is anything I
am unclear about or need to discuss further, please feel free to contact me~

Looking forward to your reply!