A newly disclosed critical privilege escalation vulnerability in the Linux kernel’s traffic-control subsystem, tracked as CVE-2026-46331 and nicknamed “pedit COW,” allows an unprivileged local user to gain full root access on affected systems.
A public, working proof-of-concept exploit named packet_edit_meme appeared on GitHub within 24 hours of CVE assignment on June 16, 2026.
The flaw lies in tcf_pedit_act(), the kernel function that rewrites packet headers in-flight via the act_pedit traffic-control module. It is designed to follow a standard Copy-on-Write (COW) pattern, making a private copy of a memory page before editing it.
Pedit COW Linux Kernel Flaw
The problem is that it validates the writable range before runtime offsets are resolved. Certain edit keys determine their final offset only at execution time, causing the write to land outside the private copy and directly into a shared page-cache page, potentially backing a cached executable on disk.
The bug was introduced by commit 899ee91156e5, present from Linux v5.18 through v7.1-rc7. A fix landed quietly on the netdev mailing list in late May 2026, framed as a routine data-corruption patch with no CVE and no security advisory.
The pattern mirrors Dirty Pipe, DirtyClone, and Dirty Frag, all cases in which a kernel fast path writes to a page it does not exclusively own.
What distinguishes this flaw is the entry point: unprivileged users can configure tc actions from inside a user namespace, acquiring namespace-local CAP_NET_ADMIN without any elevated privileges.
The exploit never touches the disk. It spawns a user namespace child to obtain CAP_NET_ADMIN, then uses the COW violation to corrupt the in-memory ELF image of /bin/su in the kernel page cache.
It overwrites the binary’s entry point with shellcode setgid(0) → setuid(0) → execve("/bin/sh") then triggers the poisoned image to drop a root shell. File-integrity checks return clean results throughout since the on-disk file is never modified.
| Distribution | Kernel | Result |
|---|---|---|
| RHEL 10.0 | 6.12.0-228.el10 | ROOT |
| Debian 13 Trixie | 6.12.90+deb13.1 | ROOT |
| Ubuntu 24.04.4 | 6.17.0-22 | ROOT (AppArmor bypass) |
| Ubuntu 26.04 | 7.0.0-14-generic | FAIL |
Ubuntu 24.04.4’s AppArmor restriction is bypassed via aa-exec using permissive container profiles. Ubuntu 26.04 closes that path entirely, though the underlying kernel remains vulnerable.
Affected Products and Patch Status
Red Hat confirmed RHEL 8, 9, and 10 are affected, along with OpenStack Platform, Red Hat Virtualization, and RHEL CoreOS.
Debian has patched Trixie; Debian 11 and 12 remain vulnerable. Ubuntu lists all supported releases from 18.04 through 26.04 as vulnerable as of June 25, 2026.
Install the patched kernel and reboot immediately. Prioritize multi-tenant hosts, CI/CD runners, Kubernetes nodes, and shared build machines. If patching is not yet possible, blacklist the module:
echo 'install act_pedit /bin/true' | sudo tee /etc/modprobe.d/disable-act_pedit.conf
Alternatively, disable unprivileged user namespaces user.max_user_namespaces=0 on RHEL or kernel.unprivileged_userns_clone=0 on Debian/Ubuntu, though this breaks rootless containers and sandboxed browsers.
Any host that ran the exploit should be treated as fully compromised, regardless of what file-integrity tooling reports.
Follow us on Google News , LinkedIn and X to Get More Instant Updates. Set Cyberpress as a Preferred Source in Google.