Copy Fail 2: Electric Boogaloo • Hacker News Board

Re: Copy Fail 2: Electric Boogaloo

#11

Post by cpach » Fri, May 08, 2026, 9:53 AM UTC

Does anyone know how to mitigate this one? Is it sufficient to disable the esp4/esp6/rxrpc modules?

Re: Copy Fail 2: Electric Boogaloo

#12

Post by alecco » Fri, May 08, 2026, 10:26 AM UTC

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

Re: Copy Fail 2: Electric Boogaloo

#13

Post by auscompgeek » Fri, May 08, 2026, 1:03 PM UTC

cassianoleal wrote: post #10

How is this different from Dirty Frag [0]? It seems to use the same vector. [0] https://github.com/V4bel/dirtyfrag

From what I can gather it is the exact same vulnerability.

Re: Copy Fail 2: Electric Boogaloo

#14

Post by tatersolid » Fri, May 08, 2026, 3:25 PM UTC

delamon wrote: post #3

Mindless2112 wrote: post #2

How much pain must there be until people realize we actually do need memory safety?

How would've memory safety helped here?

Because “Page-cache write into any readable file” is a memory safety bug? All of these recent Linux LPEs are memory safety issues.