3 ms·

The commit for the fix was public. Someone noticed. An exploit was published.

• ahartmetz 5mo ago
  I think I read on the bug's website that "No fix has been released". I understood that as there is no public fix, but maybe it only means it's not in a tagged version of the kernel and no hotfixed distro kernels have been released?
  • danudey 5mo ago
    The patch was posted to the kernel mailing list; someone saw the e-mail, read the patch, figured it out, and published an exploit very soon after.
  • tkel 5mo ago
    The fix has been commited to the git tree for the `netdev` linux subsystem fork. That's how it was noticed by the grsecurity guy who published an exploit. Then, it will be merged by linus either into a RC/master for the next linux minor version release, or into the patch releases branch by GregKH/Sasha for already-released versions. Or in this case, both, because it's a security fix.
    • staticassertion 5mo ago
      Spender didn't publish any exploit afaik
      • tkel 5mo ago
        Oh you're right, it was this guy (_SiCk / @encrypted_past) who replied to his post https://xcancel.com/encrypted_past/status/2052409822998392962 https://xcancel.com/encrypted_past/status/205240982299839296... https://xcancel.com/encrypted_past https://xcancel.com/encrypted_past https://github.com/0xdeadbeefnetwork https://github.com/0xdeadbeefnetwork https://github.com/0xdeadbeefnetwork/Copy_Fail2-Electric_Boogaloo https://github.com/0xdeadbeefnetwork/Copy_Fail2-Electric_Boo...