News for hackers. Stuff that matters.
Re:I Do Not Know C: Short quiz on undefined behavior (2015) by vyodaiken on Tuesday February 14, 2017 @02:01PM (#13646115)
In the referenced case the introduced error involved a reference to a null pointer but there was still no exploitable security hole. The exploit was enabled when the compiler removed an explicit check. The null dereference was an error, but it was not a security issue on its own.
Re:I Do Not Know C: Short quiz on undefined behavior (2015) by E6300 on Tuesday February 14, 2017 @02:05PM (#13646137)
Why didn't the kernel panic when it tried to access NULL?
Re:I Do Not Know C: Short quiz on undefined behavior (2015) by vyodaiken on Tuesday February 14, 2017 @05:35PM (#13647924)
Why is a compiler writer attempting to legislate the kernel address space?
Re:I Do Not Know C: Short quiz on undefined behavior (2015) by E6300 on Tuesday February 14, 2017 @07:06PM (#13648550)
Give me a break. The kernel developers know C. They know what "undefined behavior" means.