4 ms·

This vulnerability has already been disclosed and fixed in mainline, upstream longterm releases and major distribution kernels last year, I don't understand why

This vulnerability has already been disclosed and fixed in mainline, upstream longterm releases and major distribution kernels last year, I don't understand why it made the news today, am I missing something, is it slow news day or is it fear mongering? I flagged the thread because it is harmful (or time waster at best). From the comments I can see people are worried and unknowingly wasting their time checking their kernels to see if they are affected from a vulnerability that has already been fixed more than a year ago. Damn, I wasted half an hour of my time to see what really the situation is about.

matheweis 10y ago
Android patches were released a week or so ago that fixed this vulnerability. [https://source.android.com/security/bulletin/2017-04-01 https://source.android.com/security/bulletin/2017-04-01] That probably explains why it is bubbling up now. Many phones and routers will remain unpatched. The CVE was marked as highly critical and the kernel patche comments are vague at best as to the risks. The issue is not with this being on HN, the issue is with the lack of clarity about the scope and severity of the vulnerability.