[–] Mindless2112 2mo ago ↗ How much pain must there be until people realize we actually do need memory safety?
[–] cassianoleal 2mo ago ↗ How is this different from Dirty Frag [0]?It seems to use the same vector.[0] https://github.com/V4bel/dirtyfrag [–] auscompgeek 2mo ago ↗ From what I can gather it is the exact same vulnerability.
[–] cpach 2mo ago ↗ Does anyone know how to mitigate this one? Is it sufficient to disable the esp4/esp6/rxrpc modules?
[–] alecco 2mo ago ↗ People are blaming the wrong guy for breaking the embargo but via this blog post [1]:> on 2026-05-05 Steffen Klassert pushed f4c50a4034 to netdev/net.git with Cc: stable@vger.kernel.org.Once the fix is out it's usual for researchers to race to make the first exploit out of it.[1] https://afflicted.sh/blog/posts/copy-fail-2.html
6 comments
[ 3.4 ms ] story [ 25.4 ms ] threadIt seems to use the same vector.
[0] https://github.com/V4bel/dirtyfrag
> on 2026-05-05 Steffen Klassert pushed f4c50a4034 to netdev/net.git with Cc: stable@vger.kernel.org.
Once the fix is out it's usual for researchers to race to make the first exploit out of it.
[1] https://afflicted.sh/blog/posts/copy-fail-2.html