News for hackers. Stuff that matters.
Re:An Ancient Kernel Hole Is Not Closed by dom0 on Wednesday June 21, 2017 @03:28PM (#14607088)
Like my brethren say it's probably a good idea to use a "secure" memset that won't have an accident ^W ^W ^W be optimized out.
Re:An Ancient Kernel Hole Is Not Closed by loeg on Wednesday June 21, 2017 @11:33PM (#14609949)
Or keep >4kB objects off stack.
Re:An Ancient Kernel Hole Is Not Closed by radarsat1 on Thursday June 22, 2017 @10:29AM (#14612452)
I mean, that's probably a good practice. In my case I sort of had this idea that largish objects should be placed on the heap but I couldn't really figure out a good reason why, or what the limit should be, so I guess this vuln proposes both a reason and that the page limit is a good threshold.