News for hackers. Stuff that matters.
Re:An Ancient Kernel Hole Is Not Closed by PeterisP on Wednesday June 21, 2017 @07:31PM (#14608929)
There exists a fix for the vulnerability at the source, namely, a compiler feature that will add extra code that will "touch" every 4k page of the stack if large amount is allocated.

However, for that fix to be useful, every single distribution needs to recompile every single userland package and distribute it to every single user - i.e., instead of downloading a security patch, you need to download a new version of every executable on your hdd.

Re:An Ancient Kernel Hole Is Not Closed by kronos29296 on Friday June 23, 2017 @03:55AM (#14617637)
Can't the changes be gradually introduced? We change distros every year or reinstall the OS every time a new version of the distro is released. That's a newly compiled set of executables that are being installed every year.

If the distro guys just did for the next version (Atleast the guys like Debian, Fedora etc from whom most other distros are derived) wouldn't most systems be protected?

It would take a while but it wouldn't take 10 years atleast. Mass adoption is impossible but incremental changes are. If critical executables are patched then we have atleast a partially protected system right? (I am not an expert but this sounds a bit more plausible than breaking the entire userland)

Re:An Ancient Kernel Hole Is Not Closed by loeg on Wednesday June 21, 2017 @11:32PM (#14609946)
It could be limited to only programs that are setuid.
Re:An Ancient Kernel Hole Is Not Closed by stouset on Thursday June 22, 2017 @01:58AM (#14610359)
This applies generally to any program running as root (or a user with other privileges than yourself) if you can find a way to allocate a large enough segment of memory.
Re:An Ancient Kernel Hole Is Not Closed by loeg on Thursday June 22, 2017 @11:01PM (#14616862)
So setuid programs and network servers, for example.