CVE Watchtower

CVE-2026-43503Linux Linux Kernel

NVDCVSS scored by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Vulnerability Summary

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.
Severity Level
HIGH(8.8)
Published Date
May 23, 2026
Last Modified
Oct 16, 2026
PoC
Available(Metasploit)
Exploitation Status
Public exploit available
EPSS Score (30-Day)
1.99%Probability
Root Weakness (CWE)
See the MITRE CWE entry for the full definition of this weakness.
The product does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release.
CVSS v3.1 Base Metrics — Score 8.8 (HIGH)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

Affected & Patched Versions

Affected Versions
  • Linux Linux Kernel >= 3.9 and < 5.10.257
  • Linux Linux Kernel >= 5.11 and < 5.15.208
  • Linux Linux Kernel >= 5.16 and < 6.1.174
  • Linux Linux Kernel >= 6.2 and < 6.6.141
  • Linux Linux Kernel >= 6.7 and < 6.12.91
  • Linux Linux Kernel >= 6.13 and < 6.18.33
  • Linux Linux Kernel >= 6.19 and < 7.0.10
  • Linux Linux Kernel
Patched Versions
  • Linux Linux Kernel 5.10.257
  • Linux Linux Kernel 5.15.208
  • Linux Linux Kernel 6.1.174
  • Linux Linux Kernel 6.6.141
  • Linux Linux Kernel 6.12.91
  • Linux Linux Kernel 6.18.33
  • Linux Linux Kernel 7.0.10

What to do

Prioritize this fix. Exploit code is public, so attacks can follow quickly.

  1. Check whether you run Linux Linux Kernel and which version.
  2. Update to a patched version listed above, then confirm the new version.
  3. Review logs and exposed services for signs of earlier compromise.

Timeline

  • May 23, 2026Published
  • Oct 16, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Linux Linux Kernel CVEsYou are reading CVE-2026-43503. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

External References

Data last checked: Nov 20, 2026 06:34 UTC