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.
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.
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:HAttack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
Affected & Patched 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
- 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.
- Check whether you run Linux Linux Kernel and which version.
- Update to a patched version listed above, then confirm the new version.
- 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 alertsRelated Coverage
External References
- Patchhttps://git.kernel.org/stable/c/12401fcfb01f53ccc63ab0a3246570fe8f3105ee
- Patchhttps://git.kernel.org/stable/c/179f1852bdedc300e373e807cc102cd81feff196
- Patchhttps://git.kernel.org/stable/c/48f6a5356a33dd78e7144ae1faef95ffc990aae0
- Patchhttps://git.kernel.org/stable/c/989214c66884d70716d83dc1d0bf5e16287bf349
- Patchhttps://git.kernel.org/stable/c/9bc9d6d6967a2239aa57af2aa53554eddd640d20
- Patchhttps://git.kernel.org/stable/c/fbeab9555564a1b98e8582cd106dfe46c4606991
- Patchhttps://git.kernel.org/stable/c/fc6eb39c55e97df2f94ad974b8a5bbcd019da2c8
- Patchhttps://git.kernel.org/stable/c/ff375cc75f9167168db38e0464a482d5fbc8d81d
- Referencehttps://access.redhat.com/errata/RHSA-2026:19521
- Referencehttps://access.redhat.com/errata/RHSA-2026:19540
- Referencehttps://access.redhat.com/errata/RHSA-2026:19568
- Referencehttps://access.redhat.com/errata/RHSA-2026:19569
- Referencehttps://access.redhat.com/errata/RHSA-2026:19664
- Referencehttps://access.redhat.com/errata/RHSA-2026:19666
- Referencehttps://access.redhat.com/errata/RHSA-2026:19705
- Referencehttps://access.redhat.com/errata/RHSA-2026:19711
- Referencehttps://access.redhat.com/errata/RHSA-2026:19875
- Referencehttps://access.redhat.com/errata/RHSA-2026:20051
- Referencehttps://access.redhat.com/errata/RHSA-2026:20054
- Referencehttps://access.redhat.com/errata/RHSA-2026:20087
- Referencehttps://access.redhat.com/errata/RHSA-2026:20129
- Referencehttps://access.redhat.com/errata/RHSA-2026:20130
- Referencehttps://access.redhat.com/errata/RHSA-2026:20299
- Referencehttps://access.redhat.com/errata/RHSA-2026:20593
- Referencehttps://access.redhat.com/errata/RHSA-2026:21656
- Referencehttps://access.redhat.com/errata/RHSA-2026:21690
- Referencehttps://access.redhat.com/errata/RHSA-2026:21695
- Referencehttps://access.redhat.com/errata/RHSA-2026:21702
- Referencehttps://access.redhat.com/errata/RHSA-2026:23233
- Referencehttps://access.redhat.com/errata/RHSA-2026:23240
- Referencehttps://access.redhat.com/errata/RHSA-2026:23245
- Referencehttps://access.redhat.com/errata/RHSA-2026:23468
- Referencehttps://access.redhat.com/errata/RHSA-2026:23469
- Referencehttps://access.redhat.com/errata/RHSA-2026:23470
- Referencehttps://access.redhat.com/errata/RHSA-2026:23471
- Referencehttps://access.redhat.com/errata/RHSA-2026:24814
- Referencehttps://access.redhat.com/errata/RHSA-2026:25044
- Referencehttps://access.redhat.com/errata/RHSA-2026:33486
- Vendor Advisoryhttps://access.redhat.com/security/cve/CVE-2026-43503
- Issue Trackinghttps://bugzilla.redhat.com/show_bug.cgi?id=2480902
- Referencehttps://cert-portal.siemens.com/productcert/html/ssa-784472.html
- Referencehttps://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43503.json
Data last checked: Nov 20, 2026 06:34 UTC