News for hackers. Stuff that matters.
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution by ajross on Saturday February 16, 2013 @12:13AM (#5230474)
That's true, of course. But time is still a finite resource and it's possible to have a theoretical race with a window so narrow that it can't actually be exploited in feasible time. The fact that the proof of concept had to artificially open the window is evidence that this might be such a situation. It's still a hole; it just might not be big enough to push a hack through.
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution by lawnchair_larry on Saturday February 16, 2013 @12:54AM (#5230561)
You're speculating, but you're wrong, FYI. You're also wrong that the PoC requires a patch to work. That's just to make the window gaping and foolproof, basically.
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution by ajross on Saturday February 16, 2013 @12:30PM (#5232207)
Better to speculate and be wrong than assert without evidence. How long does the exploit take to run successfully on your test system? Did you even build it? I did, and it doesn't. Go away.
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution by tedunangst on Saturday February 16, 2013 @01:54PM (#5232514)
Strong disagree. "This race condition is way too small for anybody to exploit" is not the good kind of speculation.
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution by lawnchair_larry on Saturday February 16, 2013 @02:57PM (#5232749)
You asserted without evidence. I've successfully run it repeatedly. You don't have to believe me, but in dismissing the impact, you're making a common error. Probability of the event occurring naturally has very little to do with risk, particularly when there are no consequences for failing.