CVE-2026-52943

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

net: skbuff: fix missing zerocopy reference in pskb_carve helpers

pskb_carve_inside_header() and pskb_carve_inside_nonlinear() both copy the old skb_shared_info header into a new buffer via memcpy(), which includes the destructor_arg pointer (uarg) for MSG_ZEROCOPY skbs. Neither function calls net_zcopy_get() for the new shinfo, creating an unaccounted holder: every skb_shared_info with destructor_arg set will call skb_zcopy_clear() once when freed, but the corresponding net_zcopy_get() was never called for the new copy. Repeated calls drive uarg->refcnt to zero prematurely, freeing ubuf_info_msgzc while TX skbs still hold live destructor_arg pointers.

KASAN reports use-after-free on a freed ubuf_info_msgzc:

BUG: KASAN: slab-use-after-free in skb_release_data+0x77b/0x810 Read of size 8 at addr ffff88801574d3e8 by task poc/220

Call Trace: skb_release_data+0x77b/0x810 kfree_skb_list_reason+0x13e/0x610 skb_release_data+0x4cd/0x810 sk_skb_reason_drop+0xf3/0x340 skb_queue_purge_reason+0x282/0x440 rds_tcp_inc_free+0x1e/0x30 rds_recvmsg+0x354/0x1780 __sys_recvmsg+0xdf/0x180

Allocated by task 219: msg_zerocopy_realloc+0x157/0x7b0 tcp_sendmsg_locked+0x2892/0x3ba0

Freed by task 219: ip_recv_error+0x74a/0xb10 tcp_recvmsg+0x475/0x530

The skb consuming the late access still referenced the same uarg via shinfo->destructor_arg copied by pskb_carve_inside_nonlinear() without a refcount bump. This has been verified to be reliably exploitable: a working proof-of-concept achieves full root privilege escalation from an unprivileged local user on a default kernel configuration.

The fix follows the pattern of pskb_expand_head() which has the same memcpy/cloned structure. For pskb_carve_inside_header(), net_zcopy_get() is placed after skb_orphan_frags() succeeds, so the orphan error path needs no cleanup. For pskb_carve_inside_nonlinear(), net_zcopy_get() is placed after all failure points and just before skb_release_data(), so no error path needs cleanup at all -- matching pskb_expand_head() more closely and avoiding the need for a balancing net_zcopy_put().

CVSS v3
7.8
EG Score
7.8(high)
EPSS
7.8%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 30, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

net: skbuff: fix missing zerocopy reference in pskb_carve helpers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fd470f0a97b8e9a125f520265d2f3b088ffb5b8a
generic🟡 PoC Available

net: skbuff: fix missing zerocopy reference in pskb_carve helpers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ceafb893b12f23331dcc5ff9587e643c3a40ee9f
generic🟡 PoC Available

net: skbuff: fix missing zerocopy reference in pskb_carve helpers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9b40bdc2a3298225dffab8158208a0d8c6300578
generic🟡 PoC Available

net: skbuff: fix missing zerocopy reference in pskb_carve helpers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98d0912e9f841e5529a5b89a972805f34cb1c69d
generic🟡 PoC Available

net: skbuff: fix missing zerocopy reference in pskb_carve helpers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96a4713ae041cc85e712bac682cd2e644004d6c6
generic🟡 PoC Available

net: skbuff: fix missing zerocopy reference in pskb_carve helpers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8dbed691e43a50903658130bde0fcb5abc425b37
generic🟡 PoC Available

net: skbuff: fix missing zerocopy reference in pskb_carve helpers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/474d6c771d798bca84f0a140b611e36743511e18
generic🟡 PoC Available

net: skbuff: fix missing zerocopy reference in pskb_carve helpers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e0e74c59b2761a414d9f48d7bee1e45220b2427

Vendor Advisories for CVE-2026-52943(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 48× in last 7d / 61× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 23:00 UTCEG score recompute
  2. 2026-07-06 23:00 UTCVendor advisory
  3. 2026-07-06 23:00 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 11:21 UTCEG score recompute
  7. 2026-07-06 11:21 UTCVendor advisory
  8. 2026-07-06 11:21 UTCGHSA enrichment
  9. 2026-07-05 23:26 UTCEG score recompute
  10. 2026-07-05 23:26 UTCVendor advisory
  11. 2026-07-05 23:26 UTCGHSA enrichment
  12. 2026-07-05 11:47 UTCEG score recompute
  13. 2026-07-05 11:47 UTCVendor advisory
  14. 2026-07-05 11:47 UTCGHSA enrichment
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-05 00:08 UTCEG score recompute
  17. 2026-07-05 00:08 UTCVendor advisory
  18. 2026-07-05 00:07 UTCGHSA enrichment
  19. 2026-07-04 12:24 UTCEG score recompute
  20. 2026-07-04 12:24 UTCVendor advisory
  21. 2026-07-04 12:24 UTCGHSA enrichment
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-04 00:45 UTCEG score recompute
  24. 2026-07-04 00:45 UTCVendor advisory
  25. 2026-07-04 00:45 UTCGHSA enrichment
Show 36 more
  1. 2026-07-03 12:58 UTCEG score recompute
  2. 2026-07-03 12:58 UTCVendor advisory
  3. 2026-07-03 12:57 UTCGHSA enrichment
  4. 2026-07-03 01:19 UTCEG score recompute
  5. 2026-07-03 01:19 UTCVendor advisory
  6. 2026-07-03 01:19 UTCGHSA enrichment
  7. 2026-07-02 13:38 UTCEG score recompute
  8. 2026-07-02 13:38 UTCVendor advisory
  9. 2026-07-02 13:38 UTCGHSA enrichment
  10. 2026-07-02 02:00 UTCEG score recompute
  11. 2026-07-02 02:00 UTCVendor advisory
  12. 2026-07-02 02:00 UTCGHSA enrichment
  13. 2026-07-01 15:07 UTCEPSS rescore
  14. 2026-07-01 14:22 UTCEG score recompute
  15. 2026-07-01 14:22 UTCVendor advisory
  16. 2026-07-01 14:22 UTCGHSA enrichment
  17. 2026-07-01 02:44 UTCEG score recompute
  18. 2026-07-01 02:44 UTCVendor advisory
  19. 2026-07-01 02:44 UTCGHSA enrichment
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 15:05 UTCEG score recompute 7.80
  22. 2026-06-30 15:05 UTCVendor advisory
  23. 2026-06-30 15:04 UTCGHSA enrichment
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
  26. 2026-06-28 14:07 UTCEPSS rescore
  27. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  28. 2026-06-28 04:56 UTCEPSS rescore
  29. 2026-06-28 04:56 UTCEPSS rescore
  30. 2026-06-27 13:28 UTCEG score recompute
  31. 2026-06-27 13:28 UTCGHSA enrichment
  32. 2026-06-27 03:08 UTCEPSS rescore
  33. 2026-06-25 13:49 UTCEPSS rescore
  34. 2026-06-24 14:05 UTCEPSS rescore
  35. 2026-06-24 11:51 UTCEG score recompute
  36. 2026-06-24 11:50 UTCNVD updatefirst tracked

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCvn-lazyming/CVE-2026-52943
    First seen Jun 16, 2026

    This is a Linux Kernel Local Privilege Escalation PoC code for CVE-2026-52943 a use-after-free in skbuff.c, my first 0day found by me in linux kernel

    Open source ↗

Frequently asked(5)

What is CVE-2026-52943?
CVE-2026-52943 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: net: skbuff: fix missing zerocopy reference in pskb_carve helpers pskbcarveinsideheader() and pskbcarveinsidenonlinear() both copy the old skbsharedinfo header into a new buffer via memcpy(), which includes the destructorarg…
When was CVE-2026-52943 disclosed?
CVE-2026-52943 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52943 actively exploited?
CVE-2026-52943 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52943?
CVE-2026-52943 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-52943?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52943, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-52943

Explore →

Is Your Infrastructure Affected by CVE-2026-52943?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.