DEV Community

GeekBlog
GeekBlog

Posted on

Dirty Frag is a local root on a lot of Linux boxes, and the exploit landed before most patches did

If you run Linux in production and only skim kernel advisories, this is one to stop on. Dirty Frag is a local privilege escalation chain that takes a limited account all the way to root on a wide range of systems. Public exploit code appeared before most vendors had fixes in their repositories, which is the combination operations teams least want.

The name is a nod to Dirty COW and Dirty Pipe: compact, reliable, and hard to argue with once you have a foothold. Dirty Frag is not a single bug. It joins two kernel flaws, each able to write into page cache backed memory that the kernel does not exclusively own. One lives in the xfrm ESP path that handles IPsec. The other sits in RxRPC, the transport used by the Andrew File System. Researchers describe the pair as unusually reliable across kernel versions and hardware. A third variant, tracked as CVE 2026 46300 and nicknamed Fragnesia, has since widened the map.

The first identifier, CVE 2026 43284, is the ESP bug. It is rated CVSS 8.8 and dates back to a kernel change from January 2017, so it has been sitting in production kernels for nearly a decade. The second, CVE 2026 43500, is the RxRPC bug, rated CVSS 7.8 and introduced in June 2023.

This is not a rare module problem. The esp4, esp6 and rxrpc code is present, and often loaded, on virtually every major distribution. Vendor lists already cover Ubuntu from 18.04 LTS through 26.04, Red Hat Enterprise Linux, CentOS Stream, AlmaLinux, Fedora, openSUSE and OpenShift. On a normal server or workstation an unprivileged local user can reach root. In containers the same chain has been shown to cross the boundary and compromise the host, which is the scenario that should worry anyone running multi tenant workloads.

Microsoft’s security team has reported limited exploitation in the wild, and Microsoft Defender has added detection. The disclosure date was 7 May 2026. The Linux Kernel Organization pushed a mainline fix for CVE 2026 43284 the next day. Fixes for CVE 2026 43500 followed, but they did not land in every distro repository at the same moment. Red Hat says CVE 2026 43500 does not affect its products, while CVE 2026 43284 does. Ubuntu published updates for all supported releases on the day of the disclosure. AlmaLinux and CloudLinux followed within 48 hours.

The practical fix is a kernel update and a reboot. On Ubuntu the usual apt upgrade path is enough, provided you land on a fixed package: 18.04 wants linux 4.15.0 251.263 or the 5.4 backport 5.4.0 231.251 for that release; 20.04 wants 5.4.0 231.251 or the 5.15 backport; 22.04 wants 5.15.0 181.191 or the 6.8 backport; 24.04 wants 6.8.0 124.124 or the 6.17 backport; 26.04, Resolute Raccoon, wants linux 7.0.0 22.22. Red Hat, AlmaLinux and Fedora users should follow their own advisories and then reboot.

If a reboot is not possible today, you can block the known path by refusing to load esp4, esp6 and rxrpc through a modprobe config file and then regenerating initramfs. Unloading modules that are already in use may still need a reboot. Check first that the machine does not depend on IPsec tunnels or AFS file sharing, because that mitigation breaks both until a patched kernel is in place. After you patch, remove the block and rebuild initramfs so those modules can load again.

Local privilege escalation is easy to postpone because it needs a foothold. In real incidents that foothold is the routine part: a phished login, an exposed service, a weak application. What happens next often depends on whether a kernel bug like this was patched or left sitting. The full timeline, the Ubuntu package list and the temporary module block are set out in a briefing on the Dirty Frag privilege escalation in the Linux kernel, with both CVE identifiers, the affected distributions, and the steps to patch or disable the modules.

Top comments (0)