Dirtyfrag: How the Universal Linux LPE Hits Your Homelab

Dirty Frag (CVE-2026-43284 and CVE-2026-43500) gives local root via the kernel ESP and RxRPC modules. Fixed versions, patching Proxmox, Debian and Ubuntu, and the stopgap.

Terminal screen showing Linux kernel vulnerability patch commands being applied on a homelab server

What Dirty Frag is

Dirty Frag is a Linux local privilege escalation published on the oss-security list on 7 May 2026, with a full exploit, after the embargo broke. It chains two kernel bugs:

  • CVE-2026-43284 in IPsec ESP (esp4, esp6)
  • CVE-2026-43500 in RxRPC (rxrpc)

Both decrypt received network data in place, which can corrupt page-cache pages the attacker shouldn’t be able to write. The result is root for an unprivileged local user. At publication there were no patches or CVEs. Fixes followed in the days after.

Who should care: any host where something untrusted can run code. On a homelab that means LXC containers on a Proxmox host, shared shell accounts, and internet-facing services that could be compromised.

Fixed kernel versions (from the CVE records)

Kernel seriesESP fix (CVE-2026-43284)RxRPC fix (CVE-2026-43500)
5.105.10.255not listed in the CVE record
5.155.15.205not listed in the CVE record
6.16.1.171not listed in the CVE record
6.66.6.1386.6.140
6.126.12.876.12.88
6.186.18.286.18.29
7.07.0.57.0.6
mainline7.17.1

The ESP bug dates back to 4.11, the RxRPC one to 5.3. Distro kernels backport fixes under their own version numbers, so your distro’s advisory is what counts.

Patch

uname -r                       # what you're running now
# Debian / Ubuntu / Proxmox
sudo apt update && sudo apt full-upgrade
# Fedora / RHEL / Rocky / Alma
sudo dnf upgrade --refresh

Then reboot into the new kernel and check uname -r again.

Proxmox VE: apt update && apt dist-upgrade pulls the current proxmox-kernel. Migrate or shut down guests, reboot one node at a time, and check pvecm status before the next. LXC containers use the host’s kernel, so patching the host covers them. VMs need their own kernel updates.

If you can’t patch yet

Block the three modules, as given in the original disclosure. It’s covered in detail, including what it breaks, in Dirty Frag before the patch:

sudo sh -c "printf 'install esp4 /bin/false\ninstall esp6 /bin/false\ninstall rxrpc /bin/false\n' > /etc/modprobe.d/dirtyfrag.conf; rmmod esp4 esp6 rxrpc 2>/dev/null; true"

Sources: the oss-security disclosure, the CVE records for CVE-2026-43284 and CVE-2026-43500, and Sysdig’s analysis.

What’s Next

Frequently Asked Questions

What is Dirty Frag?
Two Linux kernel bugs chained into a local privilege escalation: CVE-2026-43284 in IPsec ESP (esp4/esp6) and CVE-2026-43500 in RxRPC. Both decrypt received data in place, which lets an unprivileged user corrupt page-cache pages and gain root. It was published on 7 May 2026 with a working exploit, after the embargo broke.
Does it affect a Proxmox host?
Yes, if the host runs an unfixed kernel and something untrusted can run code on it. LXC containers share the host kernel; full VMs run their own kernel, so each VM needs its own update.
How do I confirm I'm patched?
Boot the updated kernel, check uname -r, and compare it with your distribution's advisory for both CVEs. Upstream fixes landed in, for example, 6.12.87 (ESP) and 6.12.88 (RxRPC).

Get notified when new articles and designs land:

No spam. Unsubscribe any time.

Sergej Voronko
Sergej Voronko
SAP Basis · Senior Operations Manager · Linux infrastructure engineer
About the author →

[discussion]

Comments are powered by Giscus — backed by GitHub Discussions. Sign in with GitHub to join the conversation.