PoC Monitor
← All CVEs
CVE-2026-43503published 23 May 2026 11:44 UTCData: JSON · API

Linux

net: skbuff: propagate shared-frag marker through frag-transfer helpers

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.

First public PoC 33 daysafter publication · 25 Jun 2026
Public PoCs98 on GitHub · 1 Exploit-DB, Metasploit or nuclei
CVSS8.8high · scored by CNA · CWE-691
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= cef401de7be8c4e155c6746bfccf721a4fa5fab9, < fbeab9555564a1b98e8582cd106dfe46c4606991
  • >= cef401de7be8c4e155c6746bfccf721a4fa5fab9, < 179f1852bdedc300e373e807cc102cd81feff196
  • >= cef401de7be8c4e155c6746bfccf721a4fa5fab9, < 12401fcfb01f53ccc63ab0a3246570fe8f3105ee
  • >= cef401de7be8c4e155c6746bfccf721a4fa5fab9, < 989214c66884d70716d83dc1d0bf5e16287bf349
  • >= cef401de7be8c4e155c6746bfccf721a4fa5fab9, < fc6eb39c55e97df2f94ad974b8a5bbcd019da2c8
  • >= cef401de7be8c4e155c6746bfccf721a4fa5fab9, < ff375cc75f9167168db38e0464a482d5fbc8d81d
  • >= cef401de7be8c4e155c6746bfccf721a4fa5fab9, < 9bc9d6d6967a2239aa57af2aa53554eddd640d20
  • >= cef401de7be8c4e155c6746bfccf721a4fa5fab9, < 48f6a5356a33dd78e7144ae1faef95ffc990aae0

Fixed in fbeab9555564a1b98e8582cd106dfe46c4606991, 179f1852bdedc300e373e807cc102cd81feff196, 12401fcfb01f53ccc63ab0a3246570fe8f3105ee, 989214c66884d70716d83dc1d0bf5e16287bf349, fc6eb39c55e97df2f94ad974b8a5bbcd019da2c8, ff375cc75f9167168db38e0464a482d5fbc8d81d, 9bc9d6d6967a2239aa57af2aa53554eddd640d20, 48f6a5356a33dd78e7144ae1faef95ffc990aae0

Linux Linux
  • 3.9

Fixed in 0, 5.10.257, 5.15.208, 6.1.174, 6.6.141, 6.12.91, 6.18.33, 7.0.10, 7.1

Mitigation

Upgrade Linux to fbeab9555564a1b98e8582cd106dfe46c4606991 or 179f1852bdedc300e373e807cc102cd81feff196 or 12401fcfb01f53ccc63ab0a3246570fe8f3105ee or 989214c66884d70716d83dc1d0bf5e16287bf349 or fc6eb39c55e97df2f94ad974b8a5bbcd019da2c8 or ff375cc75f9167168db38e0464a482d5fbc8d81d or 9bc9d6d6967a2239aa57af2aa53554eddd640d20 or 48f6a5356a33dd78e7144ae1faef95ffc990aae0 or later.

Upgrade Linux to 0 or 5.10.257 or 5.15.208 or 6.1.174 or 6.6.141 or 6.12.91 or 6.18.33 or 7.0.10 or 7.1 or later.

Timeline

Days relative to CVE publication
t=0+7+14+21+28+35CVE published23 May 2026 · t = 0First public PoC25 Jun 2026 · t+33d

First public PoC 33 days after publication; not in CISA KEV. First PoC: 0xBlackash/CVE-2026-43503 (created 25 Jun 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

8 PoCs · 4 informational

PoCs 8
RepositoryCreatedStarsAssessment
0xBlackash/CVE-2026-43503 25 Jun 2026 +33 d 41 PoC
0xredash/CVE-2026-43503 25 Jun 2026 +33 d 41 PoC
ashrafzaryouh/CVE-2026-43503 25 Jun 2026 +33 d 41 PoC
mooder1/dirtyclone-CVE-2026-43503 26 Jun 2026 +34 d 17 PoC
gl1tch0x1/DirtyClone 28 Jun 2026 +36 d 3 PoC
entra1337/DirtyClone 29 Jun 2026 +37 d 27 PoC
SecureWithUmer/CVE-2026-43503 29 Jun 2026 +37 d 0 PoC
rjt-gupta/page-cache-corruption-lpes 22 Jul 2026 +60 d 13 PoC via PoC Index
Informational 4
RepositoryCreatedStarsAssessment
raesene/vuln_pocs 28 Oct 2022 −3.6 y 5 Informational · list
sec0x/CVE-2026-43503 26 Jun 2026 +34 d 0 Informational · write-up
douglasmun/pagecache-lpe-containment-kit 27 Jun 2026 +35 d 3 Informational · detection
lieehrdiansyah12/CVE-2026-43503 9 Jul 2026 +47 d 1 Informational · write-up
Flags · score 30
  • owner account created less than 7 days before the repo

Below the suspicion threshold (50); does not change the assessment.

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.

Other public exploits

Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.