Skip to main content
Public proof of conceptFix available

CVE-2026-43503

A public proof of concept exists; no exploitation attested.

  • Published2026-05-23
  • Fixed in7.0.10 · 6.18.33 · 6.12.91 · 6.6.141 · 6.1.174 · 5.15.208
  • WeaknessCWE-664 · CWE-691

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-05-2312:17CVE publishedNVD

Versions per branch

NVD · OSV
Linux linux kernel
BranchAffectedFixed in
7.0≥ 6.19, < 7.0.107.0.10
7.0≥ 6.19.0, < 7.0.107.0.10
6.x≥ 6.13, < 6.18.336.18.33
6.x≥ 6.13.0, < 6.18.336.18.33
6.x≥ 6.7, < 6.12.916.12.91
6.x≥ 6.7.0, < 6.12.916.12.91
6.x≥ 6.2, < 6.6.1416.6.141
6.x≥ 6.2.0, < 6.6.1416.6.141
6.1≥ 5.16, < 6.1.1746.1.174
6.1≥ 5.16.0, < 6.1.1746.1.174
5.x≥ 5.11, < 5.15.2085.15.208
5.x≥ 5.11.0, < 5.15.2085.15.208

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ cef401de7be8c4e155c6746bfccf721a4fa5fab9, < fbeab9555564a1b98e8582cd106dfe46c4606991fixed in fbeab9555564a1b98e8582cd106dfe46c4606991git
    • ≥ cef401de7be8c4e155c6746bfccf721a4fa5fab9, < 179f1852bdedc300e373e807cc102cd81feff196fixed in 179f1852bdedc300e373e807cc102cd81feff196git
    • ≥ cef401de7be8c4e155c6746bfccf721a4fa5fab9, < 12401fcfb01f53ccc63ab0a3246570fe8f3105eefixed in 12401fcfb01f53ccc63ab0a3246570fe8f3105eegit
    • ≥ cef401de7be8c4e155c6746bfccf721a4fa5fab9, < 989214c66884d70716d83dc1d0bf5e16287bf349fixed in 989214c66884d70716d83dc1d0bf5e16287bf349git
    • ≥ cef401de7be8c4e155c6746bfccf721a4fa5fab9, < fc6eb39c55e97df2f94ad974b8a5bbcd019da2c8fixed in fc6eb39c55e97df2f94ad974b8a5bbcd019da2c8git
    • ≥ cef401de7be8c4e155c6746bfccf721a4fa5fab9, < ff375cc75f9167168db38e0464a482d5fbc8d81dfixed in ff375cc75f9167168db38e0464a482d5fbc8d81dgit
    • ≥ cef401de7be8c4e155c6746bfccf721a4fa5fab9, < 9bc9d6d6967a2239aa57af2aa53554eddd640d20fixed in 9bc9d6d6967a2239aa57af2aa53554eddd640d20git
    • ≥ cef401de7be8c4e155c6746bfccf721a4fa5fab9, < 48f6a5356a33dd78e7144ae1faef95ffc990aae0fixed in 48f6a5356a33dd78e7144ae1faef95ffc990aae0git
  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 3.9no fix stated

    Not affected < 3.9 · ≥ 5.10.257, ≤ 5.10.* · ≥ 5.15.208, ≤ 5.15.* · ≥ 6.1.174, ≤ 6.1.* · ≥ 6.6.141, ≤ 6.6.* · ≥ 6.12.91, ≤ 6.12.* · ≥ 6.18.33, ≤ 6.18.*

    2 more version lines in the CVE record.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-08-05

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • bpftoolTuxCare:AlmaLinux:9.2all versions · fixed in 7.0.0-284.1101.el9_2.tuxcare.11.els17
  • kernelTuxCare:CentOS:8.5all versions · fixed in 4.18.0-348.7.1.el8_5.tuxcare.els50and 21 other packages
  • kernelTuxCare:CentOS:8.4all versions · fixed in 4.18.0-305.25.1.el8_4.tuxcare.els50and 21 other packages
  • kernelTuxCare:CentOS-Stream:8all versions · fixed in 4.18.0-553.6.1.el8_10.tuxcare.els33and 21 other packages
  • kernelTuxCare:AlmaLinux:9.6all versions · fixed in 5.14.0-570.62.1.el9_6.tuxcare.5.els17and 94 other packages
  • kernelTuxCare:AlmaLinux:9.2all versions · fixed in 5.14.0-284.1101.el9_2.tuxcare.11.els17and 49 other packages
  • kernelRed Hat:enterprise_linux:10.2all versions · fixed in 0:6.12.0-211.16.1.el10_2and 89 other packages
  • kernelRed Hat:enterprise_linux:9::baseosall versions · fixed in 0:5.14.0-687.10.1.el9_8and 47 other packages

162 more package ranges on OSV.dev

Vendor advisories

  • CVE-2026-43503 Red Hat Product Security2,866 products fixed

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

  • ICSA-26-295-16 CISA1 known affected

    Siemens SIMATIC S7-1500 TM MFP

    SIMATIC S7-1500 TM MFP - GNU/Linux subsystem

  • SSA-784472 Siemens ProductCERT1 known affected

    SSA-784472: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.1.1

    SIMATIC S7-1500 TM MFP - GNU/Linux subsystem

  • RHSA-2026:33486 Red Hat Product Security47 products fixed

    Red Hat Security Advisory: kernel security, bug fix, and enhancement update

  • RHSA-2026:25044 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.16.64 bug fix and security update

  • RHSA-2026:23240 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.21.19 bug fix and security update

28 more advisories

Full record on NVD

Fix

  1. Update Linux linux kernel to 7.0.10 · 6.18.33 · 6.12.91 · 6.6.141 · 6.1.174 · 5.15.208
  2. Vendor fix Red Hat Product Security RHSA-2026:33486 · 47 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
  3. Vendor fix Red Hat Product Security RHSA-2026:25044 · 4 productsFor OpenShift Container Platform 4.16 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  4. Vendor fix Red Hat Product Security RHSA-2026:23240 · 4 productsFor OpenShift Container Platform 4.21 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  5. Vendor fix Red Hat Product Security RHSA-2026:23233 · 4 productsFor OpenShift Container Platform 4.15 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  6. Vendor fix Red Hat Product Security RHSA-2026:23245 · 4 productsFor OpenShift Container Platform 4.19 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  7. Vendor fix Red Hat Product Security RHSA-2026:24814 · 35 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

Detection

read 2026-11-10 09:41 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
1 moduleexploit/linux/local/dirtyclone_cve_2026_43503rank: normalModule metadata: Metasploit Framework, © Rapid7, Inc., BSD-3-Clause.
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Published
2026-05-23
Last Modified
2026-10-16
NVD status
Modified
MSRC Title
net: skbuff: propagate shared-frag marker through frag-transfer helpers
GitHub Advisory
GHSA-494p-q444-9xf7

Frequently asked questions

What is CVE-2026-43503?

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.

Is CVE-2026-43503 actively exploited?

Active exploitation of CVE-2026-43503 has not been confirmed. Its EPSS score was 2.0% on 2026-11-15, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-43503?

CVE-2026-43503 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record