2 ms·

If this was patched in 2013 why is it an issue now?

• tedunangst 12y ago
  Because it was "silently" fixed so nobody applied the patch to existing, shipping systems.
  • mikeash 12y ago
    From what I can gather, it wasn't originally thought to be a security vulnerability so it was thought to be acceptable to leave it be on older systems. Now somebody has figured out how to exploit it.
  • tikums 12y ago
    Sweeping-under-rug is a common approach. It seems that in this instance, they have followed Linus Torvalds mantra, who once said: "I don't have any reason what-so-ever to think it's a good idea to track security bugs and announce them as something special. I don't think some spectacular security hole should be glorified or cared about as being any more special than a random spectacular crash due to bad locking."