CVE-2026-43503: Linux kernel · net: skbuff: propagate shared-frag marker through frag-transfer helpers
Affects Linux kernelSource GCVE Database
Public exploit available (Metasploit) · CVSS 8.8 High · fixed in 3.13.0-214.265 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 1.9% chance of exploitation in 30 days – higher than 80% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.13.0-214.265, 4.4.0-1156.162, 4.4.0-283.317~14.04.1 +93
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux@7.0.0-22.22?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws@7.0.0-1006.6?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure@7.0.0-1007.7?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde@7.0.0-1008.8?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp@7.0.0-1005.5?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-ibmpkg:deb/ubuntu/linux-ibm@7.0.0-1007.7?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2026-43503 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-43503 (opens in a new tab)
- git.kernel.org/linus/48f6a5356a33dd78e7144ae1faef95ffc990aae0 (opens in a new tab)
- git.kernel.org/stable/c/12401fcfb01f53ccc63ab0a3246570fe8f3105ee (opens in a new tab)
- git.kernel.org/stable/c/179f1852bdedc300e373e807cc102cd81feff196 (opens in a new tab)
- git.kernel.org/stable/c/48f6a5356a33dd78e7144ae1faef95ffc990aae0 (opens in a new tab)
- git.kernel.org/stable/c/989214c66884d70716d83dc1d0bf5e16287bf349 (opens in a new tab)
- git.kernel.org/stable/c/9bc9d6d6967a2239aa57af2aa53554eddd640d20 (opens in a new tab)
- git.kernel.org/stable/c/fbeab9555564a1b98e8582cd106dfe46c4606991 (opens in a new tab)
- git.kernel.org/stable/c/fc6eb39c55e97df2f94ad974b8a5bbcd019da2c8 (opens in a new tab)
- git.kernel.org/stable/c/ff375cc75f9167168db38e0464a482d5fbc8d81d (opens in a new tab)
- ubuntu.com/security/notices/USN-8370-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8371-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8373-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8374-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8388-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8393-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8426-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8426-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8440-1 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:19664 (opens in a new tab)
- access.redhat.com/security/updates/classification/ (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2477015 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2477802 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_19664.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:19666 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_19666.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:20051 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_20051.json (opens in a new tab)