Just an update. The fixes for DirtyFrag are pushing to stable right now. For Fedora 42, this is the 6.19.14-101 kernel. For Fedora 44 and Fedora 43, these are in the 7.0.4 kernel. There will be no 7.0.5 as it only contains a single patch which is already included in our 7.0.4 updates.
As this is a rebase kernel for Fedora 44 and Fedora 43, I have also started “offical” builds of the F42 update against F43 and F44. This gives users an option should there be a regression in 7.0.4 which makes it unusable on your system. These builds will be secure boot signed.
I pinned this globally until Monday, as there was a lot of interest in this.
For the users, the update that fixes DirtyFrag is in your daily updates. In case of a doubt, just do sudo dnf update --refresh (all updates) or sudo dnf update --security --refresh (only security updates; the fixed kernel will be contained)
I thought I read that 7.0.4 was only a partial fix, but I don’t see 7.0.6 building in Koji yet.
The 7.0.6 announcement was Monday morning US time, so around 36-ish hours or more. I thought new kernels, especially if they had a security fix, hit the koji server pretty quickly.
The patch of the official kernel 7.0.6 upstream (7.0.6. contains only one patch) seems to be already contained in our Fedora 7.0.4 build: rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present
Update: Fragnesia-fixed kernel is ready. It is in your daily updates. If you want to be sure to have it immediately, do sudo dnf update --security and then reboot!
ssh-keysign-pwn is already covered by 7.0.8 itself.
The advice for users is as usual: do your daily updates. If you feel you have a very security sensitive use case, feel free to do it bi-daily but with at least 6 hours in between both updates.
In case of a doubt: sudo dnf update --security covers security-relevant updates, including kernel.
Keep in mind that after kernel updates, you need to reboot to use the new kernel!
Fragnesia is not fixed at all upstream because every time a patch is posted, people find another exploitable code path. 7.0.8 had the v4 patch for it. 7.0.9-102 building now has the v5 patch. So yes, when 7.0.8 was built, it did have full coverage of what was known at the time. But no, it does not cover everything we know now.
Feel free to contribute to testing. Things are quite quick at the moment. The more people help to test, the quicker we can ship all security updates to users.