DirtyClone Linux Kernel LPE Flaw Lets Local Users Gain Root Access

A newly disclosed high-severity vulnerability in the Linux kernel, dubbed DirtyClone (CVE-2026-43503), allows any unprivileged local user to silently gain root access by corrupting file-backed memory via cloned network packets, leaving no kernel logs or audit traces.

DirtyClone is the latest identified variant within the DirtyFrag vulnerability family, a class of Linux kernel memory corruption bugs rooted in how socket buffers (skbs) reference shared page-cache memory, which were subsequently weaponized via in-place cryptographic transformations in the XFRM/IPsec or RxRPC subsystems.

During an audit of recent Linux kernel patches, JFrog Security Research discovered that, despite fixes for DirtyFrag (CVE-2026-43284) and its variant, Fragnesia (CVE-2026-46300), a critical residual gap persisted.

The SKBFL_SHARED_FRAG safety flag: a kernel metadata bit marking socket buffers that reference shared, file-backed page cache memory was not correctly propagated through the __pskb_copy_fclone() helper during packet cloning.

DirtyClone Linux Kernel LPE Flaw

This missing flag allowed the same exploitation class to persist through a different packet-processing path, specifically the TEE netfilter target’s internal packet-duplication mechanism.

As illustrated in the vulnerability relationship diagram above, DirtyFrag, Fragnesia, and DirtyClone are sibling vulnerabilities, not a sequential exploit chain.

Each represents a different code path where the SKBFL_SHARED_FRAG flag was dropped, bypassing the same underlying mitigation.

VulnerabilityCVEDisclosedSubsystemWrite PrimitiveRoot Required?
Copy FailCVE-2026-31431April 30, 2026algif_aead (AF_ALG crypto)4-byte page-cache writeNo
DirtyFragCVE-2026-43284 / CVE-2026-43500May 8, 2026IPsec ESP (xfrm) + RxRPCFull write primitive (chained)No
FragnesiaCVE-2026-46300May 14, 2026XFRM ESP-in-TCPArbitrary byte writeNo
DirtyCloneCVE-2026-43503May 23, 2026XFRM/IPsec via netfilter TEEFlag dropped in __pskb_copy_fclone(), triggered by TEE netfilter ruleNo

The attack exploits a kernel design intersection in which the same physical memory page simultaneously serves as file data (page cache) and network packet data (skb), enabling a controlled write to read-only, file-backed memory.

DirtyFrag Familiy (Source: jfrog)
DirtyFrag Familiy (Source: jfrog)

The attacker begins by mapping a privileged binary such as /usr/bin/su into memory, loading it into the page cache as the target. Using vmsplice and splicePage-cache-backed memory is then attached directly to a network packet (skb) without copying it.

A loopback-based IPsec tunnel is configured alongside a netfilter TEE rule that forces packet duplication via __pskb_copy_fclone() at this stage, the cloned skb silently loses the SKBFL_SHARED_FRAG flag.

The cloned skb is then routed through the local IPsec receive path to esp_input(). With the safety flag absent, the kernel skips the copy-on-write protection and decrypts directly into the file-backed page.

By manipulating AES-CBC key material, IV, and packet layout, the attacker forces predictable output bytes at chosen offsets inside /usr/bin/su‘s memory page.

JFrog Researcher stated that when the binary is next executed, Linux reuses the modified cached page and bypasses authentication checks entirely, escalating to root.

Critically, the file on disk remains entirely unchanged throughout this process, making the attack invisible to on-disk integrity monitoring tools.

Affected Systems

The full disclosure timeline shows how the vulnerability progressed from DirtyFrag’s initial landing on May 4 through to public blog publication on June 24, a 51-day window during which partially patched systems remained exploitable via this bypass.

Confirmed vulnerable distributions include Debian, Ubuntu, and Fedora, specifically where unprivileged user namespaces are enabled by default, allowing any local user to obtain CAP_NET_ADMIN inside a new namespace.

Any kernel missing the complete fix chain across CVE-2026-43284, CVE-2026-43500, CVE-2026-46300, and CVE-2026-43503 remains exposed.

The highest-risk environments are multi-tenant cloud servers, Kubernetes clusters, and containerized workloads where user namespaces are enabled, or privileged containers are deployed.

Mitigation and Patching

The primary fix is to update to Linux kernel v7.1-rc5 or apply the backported distribution patch for CVE-2026-43503. The class-wide fix ensures SKBFL_SHARED_FRAG propagates correctly across all skb copy, clone, coalesce, GRO receive, and segment paths.

If immediate patching is not possible, the following workarounds reduce attack surface:

  • Restrict user namespaces: Set kernel.unprivileged_userns_clone=0 on Debian/Ubuntu; use user.max_user_namespaces=0 on Red Hat-based systems access.
  • Blacklist IPsec kernel modules: Block esp4, esp6, and rxrpc via /etc/modprobe.d/ this disables IPsec and AFS functionality

Follow us on Google News , LinkedIn and X to Get More Instant Updates. Set Cyberpress as a Preferred Source in Google.

Tamilselvan
Tamilselvanhttps://cyberpress.org/
Tamilselvan is an Investigative cybersecurity journalist dedicated to breaking stories on ransomware cartels, data breaches, and state-sponsored espionage.

Trending News

Related Stories