News for hackers. Stuff that matters.
Re:An Ancient Kernel Hole Is Not Closed by qb45 on Wednesday June 21, 2017 @05:42PM (#14608208)
Not really. This time it's CPU and kernel failing to provide expected behavior in some corner cases which makes otherwise correct userland programs vulnerable to attacks for no fault of their own.
Re:An Ancient Kernel Hole Is Not Closed by clarry on Wednesday June 21, 2017 @05:46PM (#14608231)
It is impossible for the CPU (without architectural changes, e.g. stack segment) and kernel to provide expected behavior in the general case. They do not know whether the userland process is trying to use the stack or just access some other mapped region. Indeed, as long as these accesses do not land upon unmapped space (or space mapped with permissions that conflict with the access), the kernel doesn't have any idea what's going on.