GamingBot@lemmy.zipMB to Gaming@lemmy.zipEnglish · 14 hours agoLinux security flaws Dirty Frag and Copy Fail are a good reminder to stay up to datewww.gamingonlinux.comexternal-linkmessage-square6fedilinkarrow-up130arrow-down11
arrow-up129arrow-down1external-linkLinux security flaws Dirty Frag and Copy Fail are a good reminder to stay up to datewww.gamingonlinux.comGamingBot@lemmy.zipMB to Gaming@lemmy.zipEnglish · 14 hours agomessage-square6fedilink
minus-square9point6@lemmy.worldlinkfedilinkEnglisharrow-up5·edit-210 hours agoBasically all running versions of Linux. Fixed versions (from here): 5.10.254 5.15.204 6.1.170 6.6.137 6.12.85 6.18.22 6.19.12 More detail from AWS: https://aws.amazon.com/security/security-bulletins/rss/2026-027-aws/ I’m not sure which distros have managed to build and release the new versions of the kernel yet (if any). Most of the big ones have posted mitigations
minus-squareTrickDacy@lemmy.worldlinkfedilinkEnglisharrow-up1·edit-29 hours agoYeah I checked and my kernel version is a few patch versions back from the applicable minor version you listed. Bummer.
minus-squareTrickDacy@lemmy.worldlinkfedilinkEnglisharrow-up1·10 hours agoI appreciate this! I had assumed everyone was pushing a fix soon if not already but you may be right that it’s sort of the opposite.
minus-square9point6@lemmy.worldlinkfedilinkEnglisharrow-up5·edit-29 hours agoThe fixes were supposed to be in place by the originally planned disclosure date in a week, however someone independently released details of the exploit so they were forced to disclose early and now we’ve got this situation
Which isn’t fixed?
Basically all running versions of Linux.
Fixed versions (from here):
More detail from AWS: https://aws.amazon.com/security/security-bulletins/rss/2026-027-aws/
I’m not sure which distros have managed to build and release the new versions of the kernel yet (if any). Most of the big ones have posted mitigations
Yeah I checked and my kernel version is a few patch versions back from the applicable minor version you listed. Bummer.
I appreciate this! I had assumed everyone was pushing a fix soon if not already but you may be right that it’s sort of the opposite.
The fixes were supposed to be in place by the originally planned disclosure date in a week, however someone independently released details of the exploit so they were forced to disclose early and now we’ve got this situation