🚨 CVE-2026-43503

June 25, 2026 Β· View on GitHub

🚨 CVE-2026-43503 β€” DirtyClone

ChatGPT Image Jun 25, 2026, 11_05_52 PM

When Shared Memory Stops Being Shared Safely.

Linux Severity CVSS Type Status

A Local Privilege Escalation vulnerability caused by improper propagation of the SKBFL_SHARED_FRAG flag inside the Linux networking stack.


πŸ“– Overview

CVE-2026-43503, nicknamed DirtyClone, is a High Severity Local Privilege Escalation (LPE) vulnerability affecting the Linux kernel networking subsystem.

The vulnerability exists because several Socket Buffer (SKB) fragment-copy routines fail to preserve the SKBFL_SHARED_FRAG flag when cloning or transferring packet fragments.

As a result, memory that should remain protected by Copy-on-Write (CoW) semantics may become writable unexpectedly, allowing a local attacker to modify read-only page-cache data under specific conditions.


⚑ Why "DirtyClone"?

The name DirtyClone reflects two key characteristics:

  • Dirty β†’ Shared page-cache memory becomes unexpectedly writable.
  • Clone β†’ Triggered during cloning or transferring SKB fragments.

Similar to previous Linux memory corruption vulnerabilities, the issue stems from incorrect handling of shared memory metadata rather than a traditional buffer overflow.


🎯 Impact

Successful exploitation may allow an attacker to:

  • πŸ”Ί Escalate privileges to root
  • πŸ›  Modify root-owned read-only files
  • πŸ’Ύ Corrupt page-cache backed memory
  • ⚠ Bypass expected Copy-on-Write protections
  • πŸ”₯ Execute arbitrary code with elevated privileges (depending on exploit chain)

🧩 Root Cause

Several networking helper functions clone or move packet fragments without copying the:

SKBFL_SHARED_FRAG

flag.

Consequently, the destination socket buffer incorrectly assumes ownership of memory that is actually shared.

This breaks the kernel's assumptions about page ownership and write protection.


πŸ”¬ Affected Functions

__pskb_copy_fclone()

skb_shift()

skb_gro_receive()

skb_gro_receive_list()

tcp_clone_payload()

skb_segment()

Each of these routines may propagate fragment references without preserving the shared-fragment state.


πŸ’₯ Attack Flow

Local User
     β”‚
     β–Ό
Create crafted networking workload
     β”‚
     β–Ό
SKB Fragment Cloning
     β”‚
     β–Ό
SKBFL_SHARED_FRAG Lost
     β”‚
     β–Ό
Shared Memory Appears Private
     β”‚
     β–Ό
Write Into Read-Only Page Cache
     β”‚
     β–Ό
Privilege Escalation

πŸ“Έ Demo

CVE-2026-43503

πŸ“Š Vulnerability Details

PropertyValue
CVECVE-2026-43503
NicknameDirtyClone
SeverityHigh
CVSS v3.18.8
Attack VectorLocal
ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeChanged
ImpactPrivilege Escalation

πŸ–₯ Affected Component

Linux Kernel

Subsystem:
net/skbuff

βœ… Fixed Kernel Versions

Stable BranchFixed Version
5.105.10.257
5.155.15.208
6.16.1.174
6.66.6.141
6.126.12.91
6.186.18.33
7.07.0.10
7.1+Fixed

πŸ›‘ Mitigation

  • Upgrade to a patched Linux kernel.
  • Restrict local shell access for untrusted users.
  • Apply the latest vendor security updates.
  • Monitor systems for privilege-escalation attempts.
  • Follow the principle of least privilege.

πŸ” Detection

Indicators may include:

  • Unexpected modification of read-only files
  • Abnormal page-cache behavior
  • Local privilege escalation attempts
  • Kernel warnings related to networking memory management

πŸ“š Technical Summary

CategoryDescription
CWEImproper State Management
Vulnerability TypeLocal Privilege Escalation
ExploitationLocal authenticated attacker
Requires RebootAfter kernel update
Remote Exploitable❌ No

🧠 Key Takeaway

DirtyClone is not a network remote exploitβ€”it is a local privilege escalation vulnerability caused by incorrect handling of shared socket-buffer fragments. Losing the SKBFL_SHARED_FRAG flag allows writes to memory that should remain protected, undermining Linux's Copy-on-Write guarantees and enabling privilege escalation under the right conditions.


⭐ Stay Updated

Kernel privilege escalation vulnerabilities continue to demonstrate how subtle memory-management mistakes can have major security consequences.

If this repository was useful, consider ⭐ starring it to support cybersecurity research and vulnerability documentation.