Post B645elGQ1RvFmIjCBk by domi@donotsta.re
 (DIR) More posts by domi@donotsta.re
 (DIR) Post #B641Z07ZTFZWIqaTbs by domi@donotsta.re
       2 likes, 0 repeats
       
       a juicy Fuck You to another “security researcher” who doesn’t know how the fuck responsible disclosure works
       
 (DIR) Post #B642Rs3d9VpRDmuMme by fossdd@chaos.social
       1 likes, 0 repeats
       
       @domi i wonder how the embargo got "broken"
       
 (DIR) Post #B642SRtxsvUIOEf9iS by domi@donotsta.re
       0 likes, 0 repeats
       
       @fossdd git push to that repo, i presume?
       
 (DIR) Post #B642mo7Oze5v5Mehs0 by ptrc@social.treehouse.systems
       1 likes, 0 repeats
       
       @domi @fossdd i mean, in the repo he mentions that an "unrelated third party" broke it2026-05-07: Submitted detailed information about the vulnerability and the exploit to the linux-distros mailing list. The embargo was set to 5 days, with an agreement that if a third party publishes the exploit on the internet during the embargo period, the Dirty Frag exploit would be published publicly.2026-05-07: Detailed information and the exploit for this vulnerability were published publicly by an unrelated third party, breaking the embargo.however. he also published his patch on the netdev ML on the same day as posting the vuln report..
       
 (DIR) Post #B642qNcvQjcm586VBg by domi@donotsta.re
       0 likes, 0 repeats
       
       @ptrc @fossdd yeah i missed thisstill. having it leaked. and leaking it further yourself. THIS IS NOT HOW YOU DO DAMAGE MANAGEMENT
       
 (DIR) Post #B643M3LSNAcqRh2HdA by ptrc@social.treehouse.systems
       1 likes, 0 repeats
       
       @domi @fossdd this one is also really funny:Thanks to the flow above, a single exploit binary works across major distributions. Even if one variant is blocked by environmental policy, the other fills the gap.like, "btw i made the exploit work by trying multiple vectors" is so fucking funny for someone who's also saying "oh someone else broke the embargo so i had to publish it"
       
 (DIR) Post #B643PLNHnPInERScnw by domi@donotsta.re
       0 likes, 0 repeats
       
       @ptrc @fossdd he’s not a dipshit (for breaking the embargo); he’s a dipshit for everything that happened after the embargo was broken
       
 (DIR) Post #B643ZzaZ8S5KqkkY8O by domi@donotsta.re
       1 likes, 0 repeats
       
       @ptrc @fossdd i kind of miss the years where the security companies would say “this is a quite nasty bug, here’s the rough outline, we’ll publish the outline after everyone patches”not only does this create a CTF for the people who really really really have autism for those. it also cuts out the script kiddies (aka: 99% of the attackers)hell. all the vulns that never got a public PoC. if you never tried figuring out a vuln for yourself, have you even fucking lived?
       
 (DIR) Post #B643il9QBTbig6EYLo by ptrc@social.treehouse.systems
       1 likes, 0 repeats
       
       @domi @fossdd not to mention he also registered the domain a few days ago already
       
 (DIR) Post #B643lsqg1LsvQ8xK4G by domi@donotsta.re
       1 likes, 0 repeats
       
       @ptrc @fossdd … likewise, i miss the times when .io domains were mostly for those silly browser games
       
 (DIR) Post #B644DxZs23ugCBTz5E by fossdd@chaos.social
       0 likes, 0 repeats
       
       @domi @ptrc I mean every bug fix in the kernel is basically that. so many other LPEs are in the kernel and got fixed in stable releases, the difference now is that somebody wrote a easy reproducer for it and publishes them
       
 (DIR) Post #B644Dy0oPtSpXk5V4q by domi@donotsta.re
       1 likes, 0 repeats
       
       @fossdd @ptrc but, you know, this is the problemnot that there are LPEs or RCEs in the kernel. that people are Dicks about there being vulns in the kernel and shit in the shared sandpit, for the purpose of “disclosure”
       
 (DIR) Post #B645elGQ1RvFmIjCBk by domi@donotsta.re
       1 likes, 0 repeats
       
       a juicy Fuck You to two “security researchers” who decided to make my blood boil tonightRE: https://donotsta.re/objects/0faf12b3-dcda-43d1-826f-d106c324bfc6
       
 (DIR) Post #B645hiYUY67AFLaiGW by domi@donotsta.re
       0 likes, 0 repeats
       
       bros. fellows. you can just not publish this. have you tried that
       
 (DIR) Post #B645p4cUuaGYhoyLom by domi@donotsta.re
       0 likes, 0 repeats
       
       @16af93 https://github.com/0xdeadbeefnetwork/Copy_Fail2-Electric_Boogaloo fresh garbage
       
 (DIR) Post #B646KEwqYsVJiPLslU by domi@donotsta.re
       0 likes, 0 repeats
       
       @16af93 what affected files. you mean /sbin/su? then you’re patching just this specific exploit, not even the entrypoint to the bug. one could find another suid binary and haxx through itbefore you can update your kernel, do more or less this:$ cat /etc/modprobe.d/eh.conf install algif_aead /bin/falseinstall esp4 /bin/falseinstall esp6 /bin/falseinstall rxrpc /bin/falseinstall xfrm_user /bin/falseinstall xfrm_algo /bin/false
       
 (DIR) Post #B646co7cWc1g18FErA by fossdd@chaos.social
       0 likes, 1 repeats
       
       @domi @16af93 the fix for all security bugs is to turn of all of my devices and never touch them again. woah just imagine
       
 (DIR) Post #B646fkGRKBDovBlqs4 by domi@donotsta.re
       0 likes, 0 repeats
       
       @fossdd @16af93 IGNORANCE IS BLISS. if your government can ignore this, SO CAN YOU /j
       
 (DIR) Post #B648doBTyk1uPNekqW by Sobex@sciences.re
       0 likes, 0 repeats
       
       @domi is this two just for the dirty frag thing, or includes the earlier copy.fail one ?
       
 (DIR) Post #B648doM7LCXKwMdFQG by domi@donotsta.re
       0 likes, 0 repeats
       
       @Sobex there are two from today.
       
 (DIR) Post #B64AxZv2vRQPrkWUng by wolf480pl@mstdn.io
       0 likes, 0 repeats
       
       @domi OOTL, which bug are xfrm_user and xfrm_algo for?
       
 (DIR) Post #B64B0OsGRkBKTnZFGC by domi@donotsta.re
       0 likes, 0 repeats
       
       @wolf480pl https://github.com/0xdeadbeefnetwork/Copy_Fail2-Electric_Boogaloo
       
 (DIR) Post #B64ujzOC1kZQhIcA1A by domi@donotsta.re
       1 likes, 0 repeats
       
       issuing correction on a previous post of mine, regarding the terror group 0xdeadbeefnetwork. you do not, under any circumstances, “gotta hand it to them”https://www.openwall.com/lists/oss-security/2026/05/07/12RE: https://donotsta.re/objects/2310f332-73dc-4e7b-85e1-bcb340bde39c
       
 (DIR) Post #B650warl79VC86py7M by domi@donotsta.re
       0 likes, 0 repeats
       
       @ptrc @fossdd 11 hours ago neither of us would have expected that what kicked off the “embargo break” by the “unrelated third-party” was a commit fucking fixing this vuln in upstream. equal parts hilarious and annoying
       
 (DIR) Post #B6Jv9htMcPXLKZrACe by domi@donotsta.re
       0 likes, 0 repeats
       
       fuck this guy thrice.https://github.com/0xdeadbeefnetwork/ssh-keysign-pwnRE: https://donotsta.re/objects/8cc9266b-9f49-4f23-9cdd-1dbdd823108d