https://sourceware.org/bugzilla/show_bug.cgi?id=27355
--- Comment #3 from Sirus Shahini <sirus.shahini at gmail dot com> --- > I would disagree with that categorization. The bug is not triggered by well > formed assembler directives, but only by fuzzed ones. The assembler > generated by gcc for example should never trigger this problem. By critical I was referring to the consequences of a successful exploitation through a crafted assembly input. Of course a normal compile of a C/C++ file won't cause that much of a trouble but in security assessment of a bug, how a malicious input is given to the vulnerable program isn't usually related to its security impact. Thanks, Sirus -- You are receiving this mail because: You are on the CC list for the bug.
