Hacker News Reader

Comment by TheDong | Hacker News Reader

That range isn't quite correct. It only impacted 4.13 kernels, and only 4.13.0-4.13.6 (inclusive, distro-dependent due to backports).

It was patched in 4.13.7 after being introduced in the 4.13.0 merge window.

This issue shouldn't have happened at all, but it was caught and patched very quickly, so relatively few real-world systems are or were affected.

which by itself is in a 4.12 vanilla code tree

That commit is correct (4c48abe91be03d191d0c20cc755877da2cb35622), but it was not in 4.12 as cut by linus.

    $ git tag --contains 4c48abe91be03d191d0c20cc755877da2cb35622
    v4.13

What is your methodology that gets that it is in the 4.12 tree?

you are right, i actually didn't check on git, my bad

Thanks!