My original message: > > Erm, kernel 13mdk was originally released on 7th March, how can it have > > fixed a vuln discovered this morning?
--- Aurelien's reply: Because it was not discovered this morning. It was discovered days ago. But for security reasons, the vuln was not public until the major distributors had prepared and tested updates. Aurelien --- Jason's reply: It's 13.1-1, that's how. BUT, it seemed to break lots in my cooker, hope it doesn't on the release system. Cheers Jason --- Well, that's two entirely different explanations. Any more candidates? Hopefully from someone who actually *knows*? :) -- adamw
