News for hackers. Stuff that matters.
Re:An Ancient Kernel Hole Is Not Closed by IshKebab on Wednesday June 21, 2017 @08:53AM (#14603293)
Is it that tough? Everything says Windows/MSVC isn't affected.
Re:An Ancient Kernel Hole Is Not Closed by mnarayan01 on Wednesday June 21, 2017 @11:48AM (#14604798)
Yes. I believe Windows requires you to specify a maximum reserved stack size in the program executable. That's...not going to happen for e.g. Linux.
Re:An Ancient Kernel Hole Is Not Closed by smhenderson on Wednesday June 21, 2017 @12:38PM (#14605345)
That's correct and any of the various MS runtime libraries simply set it by default if you didn't. Thus this error[1] (in C) and this[2] (in VB).

I remember these from pre-dotNet days but based on the second link it looks not much has changed in VB.net.

[1]https://msdn.microsoft.com/en-us/library/aa264523(v=vs.60).a... [2]https://docs.microsoft.com/en-us/dotnet/visual-basic/languag...

Re:An Ancient Kernel Hole Is Not Closed by IshKebab on Thursday June 22, 2017 @04:00AM (#14610789)
So how does it detect stack overflows past that limit?

Edit: Looks like a fix for LLVM being proposed (https://reviews.llvm.org/D9653) is just to probe every page that a stack allocation covers, rather than just the final one. Doesn't sound tough at all.

Re:An Ancient Kernel Hole Is Not Closed by clarry on Wednesday June 21, 2017 @06:08PM (#14608388)
The reservation is not particularly relevant though.