CVE-2026-43503

Published May 23, 2026

Last updated 12 days ago

CVSS high 8.8
Container Security

Overview

AI description

Automated description summarized from trusted sources.

CVE-2026-43503, dubbed "DirtyClone," is a vulnerability found within the Linux kernel's networking subsystem, specifically affecting the `net/skbuff` component. The core of the issue lies in certain "frag-transfer helpers," such as `__pskb_copy_fclone()` and `skb_shift()`, which fail to correctly propagate the `SKBFL_SHARED_FRAG` bit in `skb_shinfo()->flags` when network packet fragments (skbs) are moved between source and destination. This flag is crucial as it indicates whether the packet fragments reference shared page-cache memory. This propagation failure results in a state where the destination `skb` maintains references to shared, page-cache-backed pages but incorrectly reports that it lacks shared fragments. This discrepancy can be exploited by in-place writers, such as the ESP (Encapsulating Security Payload) input processing, which relies on the `skb_has_shared_frag()` function to determine if shared pages require copying before modification. An unprivileged user could leverage this flaw, for instance, by using an `nft 'dup to <local>'` rule or other `nf_dup_ipv4()` / `xt_TEE` callers, to write into the page cache of a root-owned read-only file.

Description
In the Linux kernel, the following vulnerability has been resolved: net: skbuff: propagate shared-frag marker through frag-transfer helpers Two frag-transfer helpers (__pskb_copy_fclone() and skb_shift()) fail to propagate the SKBFL_SHARED_FRAG bit in skb_shinfo()->flags when moving frags from source to destination. __pskb_copy_fclone() defers the rest of the shinfo metadata to skb_copy_header() after copying frag descriptors, but that helper only carries over gso_{size,segs, type} and never touches skb_shinfo()->flags; skb_shift() moves frag descriptors directly and leaves flags untouched. As a result, the destination skb keeps a reference to the same externally-owned or page-cache-backed pages while reporting skb_has_shared_frag() as false. The mismatch is harmful in any in-place writer that uses skb_has_shared_frag() to decide whether shared pages must be detoured through skb_cow_data(). ESP input is one such writer (esp4.c, esp6.c), and a single nft 'dup to <local>' rule -- or any other nf_dup_ipv4() / xt_TEE caller -- is enough to land a pskb_copy()'d skb in esp_input() with the marker stripped, letting an unprivileged user write into the page cache of a root-owned read-only file via authencesn-ESN stray writes. Set SKBFL_SHARED_FRAG on the destination whenever frag descriptors were actually moved from the source. skb_copy() and skb_copy_expand() share skb_copy_header() too but linearize all paged data into freshly allocated head storage and emerge with nr_frags == 0, so skb_has_shared_frag() returns false on its own; they need no change. The same omission exists in skb_gro_receive() and skb_gro_receive_list(). The former moves the incoming skb's frag descriptors into the accumulator's last sub-skb via two paths (a direct frag-move loop and the head_frag + memcpy path); the latter chains the incoming skb whole onto p's frag_list. Downstream skb_segment() reads only skb_shinfo(p)->flags, and skb_segment_list() reuses each sub-skb's shinfo as the nskb -- both p and lp must carry the marker. The same omission also exists in tcp_clone_payload(), which builds an MTU probe skb by moving frag descriptors from skbs on sk_write_queue into a freshly allocated nskb. The helper falls into the same family and warrants the same fix for consistency; no TCP TX-side in-place writer is currently known to reach a user page through this gap, but a future consumer depending on the marker would regress silently. The same omission exists in skb_segment(): the per-iteration flag merge takes only head_skb's flag, and the inner switch that rebinds frag_skb to list_skb on head_skb-frags exhaustion does not fold the new frag_skb's flag into nskb. Fold frag_skb's flag at both sites so segments drawing frags from frag_list members carry the marker.
Source
416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD status
Modified
Products
linux_kernel

Risk scores

CVSS 3.1

Type
Secondary
Base score
8.8
Impact score
6
Exploitability score
2
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Severity
HIGH

Weaknesses

nvd@nist.gov
NVD-CWE-noinfo
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
CWE-664

Social media

Hype score
Not currently trending
  1. Added 4 new LPE exploits to lpe-toolkit: - PEdit COW CVE-2026-46331 - DirtyClone CVE-2026-43503 - Bad Epoll CVE-2026-46242 - FUSE OOB CVE-2026-31694 https://t.co/BmdCcmBkWK

    @portbuster1337

    6 Jul 2026

    10226 Impressions

    48 Retweets

    211 Likes

    137 Bookmarks

    2 Replies

    1 Quote

  2. Tails 7.9.1 is out: https://t.co/1TZmZC8BtT It fixes CVE-2026-43503 (*DirtyClone*) and CVE-2026-46331 (*PACKET_EDIT_MEME*).

    @Tails_live

    1 Jul 2026

    4751 Impressions

    25 Retweets

    93 Likes

    6 Bookmarks

    2 Replies

    1 Quote

  3. CISO Daily Briefing: Amazon Q Developer CVE-2026-12957 (CVSS 8.5) — MCP auto-execution, no user interaction required, Miasma worm across 73 GitHub repos; Linux LPEs CVE-2026-46331 + CVE-2026-43503 bypass file integrity monitoring entirely in memory. Fable 5/Mythos 5 suspended f

    @cloudsa

    28 Jun 2026

    428 Impressions

    0 Retweets

    0 Likes

    1 Bookmark

    0 Replies

    0 Quotes

  4. Open-source defensive toolkit against #DirtyClone (CVE-2026-43503) and #peditCOW (CVE-2026-46331). While patching remains the ultimate solution, this toolkit helps you close the gap while you patch. https://t.co/2ETRhoK5oU

    @douglasmun

    28 Jun 2026

    234 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  5. Acaba de confirmarse: una nueva vulnerabilidad en el núcleo de Linux llamada DirtyClone, que permite a los atacantes escalar privilegios y reescribir ejecutables en memoria sin dejar rastro en el disco, con un exploit ya disponible para CVE-2026-43503. DirtyClone está https://

    @BotBauR

    27 Jun 2026

    126 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  6. - Copy Fail (CVE-2026-31431) - DirtyFrag (CVE-2026-43284 and CVE-2026-43500) - Fragnesia (CVE-2026-46300) - DirtyClone(CVE-2026-43503)&lt;- New https://t.co/dHXh8SMFHa

    @hakkadaikon

    27 Jun 2026

    1203 Impressions

    0 Retweets

    2 Likes

    3 Bookmarks

    0 Replies

    1 Quote

  7. CVE-2026-46331 CVE-2026-43503 アルマリナックス対応済み

    @hacker_infra

    26 Jun 2026

    206 Impressions

    0 Retweets

    2 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  8. 🚨 Successful PoC for Linux Kernel CVE-2026-43503 (DirtyFrag variant). @JFrogSecurity researchers successfully developed a privilege escalation exploit for CVE-2026-43503, a newly discovered DirtyFrag variant we dubbed "DirtyClone". The vulnerability was patched and merged in

    @jfrog

    26 Jun 2026

    410 Impressions

    1 Retweet

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  9. Three high-severity CVEs hit enterprise and dev stacks today: CVE-2026-12957 lets a malicious repo silently execute code via Amazon Q Developer's MCP config, exfiltrating AWS credentials; CVE-2026-43503 (DirtyClone, CVSS 8.8) gives Linux local users root via cloned network

    @XavierRiveraX

    26 Jun 2026

    76 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  10. Our CTI team identified a lot of activities targeting Linux Kernel (CVE-2026-43503) https://t.co/8mR3ngQvwi

    @vuldb

    24 May 2026

    72 Impressions

    1 Retweet

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

Configurations

References

Sources include official advisories and independent security research.