| |||||||||||||
|
| |||||||||||||
GCC 4.3.0 exposes a kernel bugGCC 4.3.0 exposes a kernel bugPosted Mar 7, 2008 23:59 UTC (Fri) by pleple (guest, #50447)Parent article: GCC 4.3.0 exposes a kernel bug
So the bug was there forever and, if my understanding of the problem is correct, anybody could make use of it on both Linux and BSD (well, you don't need any compiler to make executable code). Still, there is no known exploit for it. I know we can't assume that the problem ins't exploitable but i would say that this is at most very improbable. Is this reasoning correct?
(Log in to post comments)
GCC 4.3.0 exposes a kernel bug Posted Mar 8, 2008 1:52 UTC (Sat) by speedster1 (subscriber, #8143) [Link] The main concern is not that someone will *purposefully* write a program that uses this bug to clobber its own memory, so the fact that someone could have used a non-standard compiler to achieve this is not relevent. The real problem is that the new behavior would open up one more way for programmers to *accidentally* write a program that corrupts its memory, and this could be the memory corruption bug that adds up with other bugs in the application itself to result in an exploit.
|
|
||||||||||||