Securing Your Linux System Against the Dirty Frag Vulnerability: A Step-by-Step Update Guide
Overview
The Dirty Frag vulnerability (CVE-2026-43500) has been a major concern in the Linux community. This local privilege escalation (LPE) exploit was inadvertently exposed, catching many distributions off guard. Fortunately, a proper fix has been released in Linux kernel versions 7.0.6 and 6.18.29 LTS. The patch, authored by researcher Hyunwoo Kim, addresses a root cause dating back to a 2019 commit. Two packet types—those fed via splice() and those with fragment chains—were not treated as shared memory, allowing a local attacker to modify pages during decryption and gain root access. The fix extends existing checks to ensure these packets are copied to a private buffer before decryption.

This guide will walk you through updating your system to protect against Dirty Frag, whether you are using Fedora, Pop!_OS, or prefer manual kernel installation. We’ll cover prerequisites, step-by-step instructions, common pitfalls, and a summary of key points.
Prerequisites
Before proceeding, ensure you have:
- Root or sudo access to your system.
- A backup of important data—kernel updates, especially manual ones, carry risk.
- Knowledge of basic command-line operations.
- One of the following distributions (or equivalent): Fedora (version 42, 43, or 44) or Pop!_OS (22.04 or 24.04 LTS). If you are on a different distro, a manual kernel update is possible but not covered in detail here.
- An active internet connection to download updates.
Step-by-Step Instructions
Updating on Fedora
Fedora kernel maintainer Justin Forbes announced that the fix was pushed to the stable branch before the official 7.0.6 release. Fedora 43 and 44 receive the patched kernel 7.0.4-100, while Fedora 42 gets it with kernel 6.19.14-101. Note that Fedora skipped 7.0.5 because 7.0.4 already included the patch.
- Check for available updates: Open a terminal and run:
sudo dnf update
This lists pending updates without installing them. Verify that the kernel package is included (e.g.,kernel-7.0.4-100.fc43.x86_64). - Apply the upgrade: Once confirmed, execute:
sudo dnf upgrade
When prompted, typeYand press Enter to proceed. - Reboot to load the new kernel:
sudo reboot
After reboot, you can verify the running kernel with uname -r. It should show the patched version.
Updating on Pop!_OS
System76 released kernel updates for Pop!_OS 22.04 and 24.04 LTS that cover both Dirty Frag CVEs. For the rxrpc module, they chose to disable it rather than patch, while the esp4 and esp6 modules were patched and are safe to re-enable.
- Update package lists and upgrade: Run:
sudo apt update && sudo apt upgrade
This will fetch and install the latest kernel and related packages. - Reboot to apply the changes:
sudo reboot
After reboot, confirm the kernel version with uname -r. It should be a version that includes the Dirty Frag fix (e.g., 6.18.29 or later customized builds).
Manual Kernel Installation (Advanced Users)
If you are on a distribution not yet covered, or prefer to apply the patch yourself, you can manually install kernel 7.0.6 from kernel.org. Warning: This is risky and should only be attempted by experienced users. Always back up your data first.
- Download the tarball from kernel.org (search for linux-7.0.6.tar.xz).
- Extract and configure: Use
tar -xvf linux-7.0.6.tar.xz, thencd linux-7.0.6and configure withmake menuconfig(or copy your current config from/boot). - Build and install: Run
make -j$(nproc)followed bysudo make modules_install install. - Update bootloader (e.g.,
sudo update-grubon Debian/Ubuntu) and reboot. - Verify with
uname -r. It should show 7.0.6.
For Ubuntu-based distributions, refer to our separate guide for detailed manual installation steps.
Common Mistakes
- Forgetting to reboot: After updating the kernel, you must reboot to start using the new version. Running
uname -rwithout rebooting will show the old kernel. - Skipping backup: Manual kernel installation can break your system if misconfigured. Always back up critical data.
- Using wrong package manager: Fedora uses
dnf, while Pop!_OS usesapt. Running the wrong command will fail. - Not checking repository state: Ensure your package lists are up-to-date (run
sudo dnf check-updateorsudo apt updatebefore upgrading). - Assuming all packages are updated: The kernel update may be separate from other updates. Verify that the kernel package is included in the list.
- Ignoring LTS specific versions: If you are on Fedora 42, you get a different kernel version than Fedora 43/44. Make sure you are running the correct update for your release.
- Disabled modules not re-enabled: On Pop!_OS, the
rxrpcmodule is disabled. Do not attempt to re-enable it until System76 confirms it is safe. Theesp4andesp6modules are safe to re-enable if you need IPsec ESP acceleration.
Summary
The Dirty Frag vulnerability (CVE-2026-43500) is a high-severity LPE in the Linux kernel’s rxrpc handling. It has been fully patched in kernel 7.0.6 and 6.18.29 LTS. Fedora and Pop!_OS users can update via their package managers (dnf or apt) and reboot. Advanced users can compile and install manually. Always back up data, verify the kernel version after update, and avoid common pitfalls like forgetting to reboot. Stay secure by keeping your kernel up to date.
Related Articles
- Meta's Latest Enhancements for End-to-End Encrypted Backups: A Q&A Guide
- Record-Breaking Patch Tuesday: 167 Flaws Fixed, Zero-Day Under Active Attack – Microsoft, Google, Adobe Issue Urgent Updates
- 7 Critical Insights into the Killswitch Approach for Emergency Vulnerability Mitigation
- Mastering Container Security: 7 Key Questions on Docker Hardened Images and Mend.io Integration
- Mastering Oracle's Monthly Critical Patch Update Program: A Comprehensive Guide
- Cybersecurity Roundup: SMS Blaster Fraud, OpenEMR Vulnerabilities, and Massive Roblox Breach
- April 2026 Patch Tuesday: Record-Breaking Security Updates and Actively Exploited Vulnerabilities
- Meta Unveils Major Security Upgrades for Encrypted Backups: Fleet Key Distribution and Transparency Initiative