git404hub

what is dirtyclone fr?

entra1337/dirtyclone — explained in plain English

Analysis updated 2026-05-18

21PythonAudience · researcherComplexity · 4/5Setup · moderate

tl;dr

A Python proof-of-concept exploit for a Linux kernel privilege escalation bug (CVE-2026-43503), for authorized security research only.

vibe map

mindmap
  root((DirtyClone))
    What it does
      Kernel PoC exploit
      CVE-2026-43503
    Tech stack
      Python
      Linux kernel
    Use cases
      Study the bug safely
      Verify patch status
      Security research reference
    Audience
      Security researchers
    Notes
      Educational use only
      Requires vulnerable kernel

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Study, in a lab environment, how a Linux kernel page-cache bug can be escalated to root access.

VIBE 2

Verify whether a specific kernel build is vulnerable to CVE-2026-43503 before patching.

VIBE 3

Use as a reference PoC when writing a security advisory or patch validation test.

what's the stack?

PythonLinux kernel

how it stacks up fr

entra1337/dirtyclone0whitedev/detranspiler2951461586/mulerun-pool
Stars212121
LanguagePythonPythonPython
Setup difficultymoderatehardmoderate
Complexity4/54/53/5
Audienceresearcherdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Only works on a narrow range of vulnerable kernel builds with unprivileged user namespaces enabled, for authorized research only.

Not stated in the README.

in plain english

DirtyClone is a proof of concept exploit for a security flaw in the Linux kernel, tracked as CVE-2026-43503. It is written entirely in Python and demonstrates how a regular, unprivileged user on an affected Linux system could gain full root access. The README describes it as an independent, non-official Python reimplementation of a technique originally researched by JFrog Security Research, and calls it the fourth vulnerability in a related family that also includes earlier bugs known as DirtyPipe and DirtyFrag. According to the README, the underlying issue involves how the Linux kernel handles copied network socket buffers when a specific netfilter feature is combined with an encrypted networking protocol. Because of a flag handling mistake, data that should stay isolated can end up written directly into memory that is shared with files on disk, which is the page cache the operating system uses to speed up file access. The README rates the severity of this bug as high, states it affects a narrow range of Linux kernel release candidates before a specific fix commit, and notes it only works when a particular kernel setting for unprivileged user namespaces is turned on. The proof of concept itself is described as pure Python with no compilation step required. Once run, it is said to add a new user with root level permissions to the system's password file and then open an interactive root shell for the attacker. The README describes the code as clean and commented. The project includes a clear disclaimer stating it is meant only for educational and security research purposes, and that using it against systems the user does not own or have explicit permission to test is illegal. It links to the CVE record and the kernel commit that eventually fixed the issue, though a link to the original research writeup is not yet filled in.

prompts (copy fr)

prompt 1
Explain in plain terms what CVE-2026-43503 is and how this Python PoC is supposed to demonstrate it.
prompt 2
What kernel versions and settings does this README say are required for DirtyClone to work?
prompt 3
Summarize the disclaimer and legal boundaries this README sets for using this exploit.

Frequently asked questions

what is dirtyclone fr?

A Python proof-of-concept exploit for a Linux kernel privilege escalation bug (CVE-2026-43503), for authorized security research only.

What language is dirtyclone written in?

Mainly Python. The stack also includes Python, Linux kernel.

What license does dirtyclone use?

Not stated in the README.

How hard is dirtyclone to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is dirtyclone for?

Mainly researcher.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.