CVE-2026-43503

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

HIGH
8.8
CVSS Score
Published: May 23, 2026 at 11:44 AM UTC
Updated: October 16, 2026 at 07:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: preserve shared-frag marker during coalescing skb_try_coalesce() can attach paged frags from @from to @to. If @from has SKBFL_SHARED_FRAG set, the resulting @to skb can contain the same externally-owned or page-cache-backed frags, but the shared-frag marker is currently lost. That breaks the invariant relied on by later in-place writers. In particular, ESP input checks skb_has_shared_frag() before deciding whether an uncloned nonlinear skb can skip skb_cow_data(). If TCP receive coalescing has moved shared frags into an unmarked skb, ESP can see skb_has_shared_frag() as false and decrypt in place over page-cache backed frags. Propagate SKBFL_SHARED_FRAG when skb_try_coalesce() transfers paged frags. The tailroom copy path does not need the marker because it copies bytes into @to's linear data rather than transferring frag descriptors.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.9 ≤ v < 5.10.2575.11 ≤ v < 5.15.2085.16 ≤ v < 6.1.1746.13 ≤ v < 6.18.336.19 ≤ v < 7.0.106.2 ≤ v < 6.6.1416.7 ≤ v < 6.12.917.17.1 rc17.1 rc27.1 rc37.1 rc4cef401de7be8c4e155c6746bfccf721a4fa5fab9
Vendor states this is fixed in 12401fcfb01f53ccc63ab0a3246570fe8f3105ee (fixed)
Vendor states this is fixed in 179f1852bdedc300e373e807cc102cd81feff196 (fixed)
Vendor states this is fixed in 48f6a5356a33dd78e7144ae1faef95ffc990aae0 (fixed)
Vendor states this is fixed in 989214c66884d70716d83dc1d0bf5e16287bf349 (fixed)
Vendor states this is fixed in 9bc9d6d6967a2239aa57af2aa53554eddd640d20 (fixed)
Vendor states this is fixed in fbeab9555564a1b98e8582cd106dfe46c4606991 (fixed)
Vendor states this is fixed in fc6eb39c55e97df2f94ad974b8a5bbcd019da2c8 (fixed)
Vendor states this is fixed in ff375cc75f9167168db38e0464a482d5fbc8d81d (fixed)
Vendor states this is fixed in 3.9 (unaffected)
Vendor states this is fixed in 5.10.257 (unaffected)
Vendor states this is fixed in 5.15.208 (unaffected)
Vendor states this is fixed in 6.1.174 (unaffected)
Vendor states this is fixed in 6.12.91 (unaffected)
Vendor states this is fixed in 6.18.33 (unaffected)
Vendor states this is fixed in 6.6.141 (unaffected)
Vendor states this is fixed in 7.0.10 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfoCWE-664CWE-691

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card