CVE-2026-43284

CRITICALPre-NVD 7.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 93% probability of exploitation within the next 30 days (top 0.2% of all CVEs). CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8 retained for reference (NVD's own analysis pending). Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: cisa-adp, epss, ghsa
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Metasploit, ssvc poc, public exploit)
CISA-KEV: Not listedEPSS PROB: 2.5%CVSS: 7.8Exploit: Metasploit · ssvc poc · public exploitExposed services: Not assessed

A fix is available — apply it.

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

xfrm: esp: avoid in-place decrypt on shared skb frags

MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(), so later paths that may modify packet data can first make a private copy. The IPv4/IPv6 datagram append paths did not set this flag when splicing pages into UDP skbs.

That leaves an ESP-in-UDP packet made from shared pipe pages looking like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW fast path for uncloned skbs without a frag_list and decrypts in place over data that is not owned privately by the skb.

Mark IPv4/IPv6 datagram splice frags with SKBFL_SHARED_FRAG, matching TCP. Also make ESP input fall back to skb_cow_data() when the flag is present, so ESP does not decrypt externally backed frags in place. Private nonlinear skb frags still use the existing fast path.

This intentionally does not change ESP output. In esp_output_head(), the path that appends the ESP trailer to existing skb tailroom without calling skb_cow_data() is not reachable for nonlinear skbs: skb_tailroom() returns zero when skb->data_len is nonzero, while ESP tailen is positive. Thus ESP output will either use the separate destination-frag path or fall back to skb_cow_data().

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
78
EG Risk 78/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation93% × 40%
Automatability0% × 15%
EPSS PROB
2.5%
EPSS %ILE
83rd
KEV
Not listed

Published

May 8, 2026

Last Modified

September 8, 2026

Advisory Details (10)

Auto-updated May 11, 2026
Patch available.
generic

xfrm: esp: ipv4: fix up flags setting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fe785bb3a8096dffcc4048a85cd0c83337eeecad
generic

xfrm: esp: avoid in-place decrypt on shared skb frags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f4c50a4034e62ab75f1d5cdd191dd5f9c77fdff4
generic

xfrm: esp: avoid in-place decrypt on shared skb frags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b54edf1e9a3fd3491bdcb82a21f8d21315271e0d
generic

xfrm: esp: avoid in-place decrypt on shared skb frags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ab8b995323e5237041472d07e5055f5f7dcdf15b
generic

xfrm: esp: avoid in-place decrypt on shared skb frags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a6cb440f274a22456ef3e86b457344f1678f38f9
generic

xfrm: esp: ipv4: fix up flags setting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8253aab4659ca16116b522203c2a6b18dccacea7
generic

xfrm: esp: avoid in-place decrypt on shared skb frags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71a1d9d985d26716f74d21f18ee8cac821b06e97
generic

xfrm: esp: avoid in-place decrypt on shared skb frags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d55c7336f8032d434adcc5fab987ccc93a44aec
generic

xfrm: esp: avoid in-place decrypt on shared skb frags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52646cbd00e765a6db9c3afe9535f26218276034
generic

xfrm: esp: avoid in-place decrypt on shared skb frags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50ed1e7873100f77abad20fd31c51029bc49cd03

Patch Availability(25)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhcos-417.94.202606250942-02026-07-09redhat
redhatkernel-0:6.12.0-231.12.el10nv2026-06-30redhat
redhatrhcos-413.92.202606160406-02026-06-25redhat
redhatrhcos-415.92.202606030318-02026-06-11redhat
redhatrhcos-412.86.202605271418-02026-06-04redhat
redhatkpatch-patch2026-05-20redhat
redhatkernel-0:6.12.0-211.16.1.el10_22026-05-20redhat
redhatkernel-0:5.14.0-687.10.1.el9_82026-05-20redhat
redhatkernel-0:5.14.0-687.5.3.el9_82026-05-19redhat
redhatkernel-0:6.12.0-211.7.3.el10_22026-05-19redhat
redhatkernel-0:6.12.0-211.7.el10nv2026-05-15redhat
redhatrhcos-412.86.202605111404-02026-05-14redhat
redhatrhcos-414.92.202605111427-02026-05-14redhat
redhatrhcos-4.20.9.6.202605110206-02026-05-13redhat
redhatrhcos-4.21.9.6.202605110143-02026-05-13redhat
redhatrhcos-4.19.9.6.202605110225-02026-05-13redhat
redhatkernel-0:5.14.0-570.113.1.el9_62026-05-13redhat
redhatrhcos-418.94.202605101521-02026-05-13redhat
redhatrhcos-416.94.202605101426-02026-05-13redhat
redhatkernel-0:4.18.0-372.192.1.el8_62026-05-12redhat
redhatkernel-rt-0:4.18.0-553.124.1.rt7.465.el8_102026-05-12redhat
redhatkernel-0:4.18.0-305.191.1.el8_42026-05-12redhat
redhatkernel-rt-0:5.14.0-70.179.1.rt21.251.el9_02026-05-12redhat
redhatkernel-0:6.12.0-55.73.1.el10_02026-05-12redhat
linuxKernel @ 5.10.255 (fixes >=4.11.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (51 versions)
  • every version up to 5.10.251-4: fixed in 5.10.251-4
—
linux-6.16.1.106-3~deb11u1 ... 6.1.170-1~deb11u1 (17 versions)
  • every version up to 6.1.170-3~deb11u1: fixed in 6.1.170-3~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (50 versions)
  • every version up to 6.1.170-3: fixed in 6.1.170-3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.86-1~bpo12+1 (19 versions)
  • every version up to 6.12.86-1: fixed in 6.12.86-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (135 versions)
  • every version up to 7.0.4-1: fixed in 7.0.4-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(20)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 19× 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.

Showing the most recent 100 of 268 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-01 19:50 UTCEPSS rescore
  4. 2026-09-30 15:03 UTCEPSS rescore
  5. 2026-09-28 02:02 UTCOSV refresh
  6. 2026-09-27 13:48 UTCEPSS rescore
  7. 2026-09-26 15:58 UTCEPSS rescore
  8. 2026-09-17 19:31 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-08 09:46 UTCEG score recompute
  13. 2026-09-08 09:46 UTCVendor advisory
  14. 2026-09-08 09:46 UTCGHSA enrichment
  15. 2026-09-08 09:31 UTCNVD updateCVSS v3 → 7.8
  16. 2026-09-08 09:02 UTCEG score recompute
  17. 2026-09-08 09:02 UTCVendor advisory
  18. 2026-09-08 09:01 UTCGHSA enrichment
  19. 2026-09-06 13:47 UTCEPSS rescore
  20. 2026-09-01 12:22 UTCEG score recompute
  21. 2026-09-01 12:22 UTCVendor advisory
  22. 2026-09-01 12:21 UTCGHSA enrichment
  23. 2026-08-30 19:17 UTCEPSS rescore
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-26 14:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 12:26 UTCEG score recompute
  3. 2026-08-24 12:26 UTCVendor advisory
  4. 2026-08-24 12:26 UTCGHSA enrichment
  5. 2026-08-23 19:28 UTCEG score recompute
  6. 2026-08-23 19:28 UTCVendor advisory
  7. 2026-08-23 19:27 UTCGHSA enrichment
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-17 11:58 UTCVendor advisory
  10. 2026-08-17 11:58 UTCGHSA enrichment
  11. 2026-08-16 09:12 UTCVendor advisory
  12. 2026-08-16 09:12 UTCGHSA enrichment
  13. 2026-08-16 04:40 UTCEG score recompute
  14. 2026-08-16 04:40 UTCVendor advisory
  15. 2026-08-16 04:40 UTCGHSA enrichment
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 00:15 UTCVendor advisory
  18. 2026-08-15 00:15 UTCGHSA enrichment
  19. 2026-08-14 20:03 UTCVendor advisory
  20. 2026-08-14 20:03 UTCGHSA enrichment
  21. 2026-08-14 15:51 UTCVendor advisory
  22. 2026-08-14 15:51 UTCGHSA enrichment
  23. 2026-08-14 11:39 UTCVendor advisory
  24. 2026-08-14 11:39 UTCGHSA enrichment
  25. 2026-08-14 07:27 UTCVendor advisory
  26. 2026-08-14 07:27 UTCGHSA enrichment
  27. 2026-08-14 03:15 UTCVendor advisory
  28. 2026-08-14 03:14 UTCGHSA enrichment
  29. 2026-08-13 10:48 UTCVendor advisory
  30. 2026-08-13 10:48 UTCGHSA enrichment
  31. 2026-08-13 06:00 UTCVendor advisory
  32. 2026-08-13 06:00 UTCGHSA enrichment
  33. 2026-08-13 01:30 UTCVendor advisory
  34. 2026-08-13 01:30 UTCGHSA enrichment
  35. 2026-08-12 21:18 UTCVendor advisory
  36. 2026-08-12 21:18 UTCGHSA enrichment
  37. 2026-08-12 16:50 UTCEG score recompute
  38. 2026-08-12 16:50 UTCVendor advisory
  39. 2026-08-12 16:50 UTCGHSA enrichment
  40. 2026-08-12 13:51 UTCEPSS rescore
  41. 2026-08-12 00:29 UTCVendor advisory
  42. 2026-08-12 00:29 UTCGHSA enrichment
  43. 2026-08-11 20:08 UTCVendor advisory
  44. 2026-08-11 20:08 UTCGHSA enrichment
  45. 2026-08-11 15:53 UTCEG score recompute
  46. 2026-08-11 15:53 UTCVendor advisory
  47. 2026-08-11 15:53 UTCGHSA enrichment
  48. 2026-08-11 10:36 UTCVendor advisory
  49. 2026-08-11 10:36 UTCGHSA enrichment
  50. 2026-08-11 05:33 UTCVendor advisory
  51. 2026-08-11 05:33 UTCGHSA enrichment
  52. 2026-08-11 01:21 UTCVendor advisory
  53. 2026-08-11 01:21 UTCGHSA enrichment
  54. 2026-08-10 12:09 UTCVendor advisory
  55. 2026-08-10 12:09 UTCGHSA enrichment
  56. 2026-08-10 07:53 UTCVendor advisory
  57. 2026-08-10 07:53 UTCGHSA enrichment
  58. 2026-08-10 03:41 UTCVendor advisory
  59. 2026-08-10 03:41 UTCGHSA enrichment
  60. 2026-08-09 23:29 UTCVendor advisory
  61. 2026-08-09 23:29 UTCGHSA enrichment
  62. 2026-08-09 19:17 UTCVendor advisory
  63. 2026-08-09 19:17 UTCGHSA enrichment
  64. 2026-08-09 15:05 UTCVendor advisory
  65. 2026-08-09 15:05 UTCGHSA enrichment
  66. 2026-08-09 10:53 UTCVendor advisory
  67. 2026-08-09 10:53 UTCGHSA enrichment
  68. 2026-08-09 06:39 UTCVendor advisory
  69. 2026-08-09 06:39 UTCGHSA enrichment
  70. 2026-08-09 02:27 UTCVendor advisory
  71. 2026-08-09 02:27 UTCGHSA enrichment
  72. 2026-08-08 10:02 UTCVendor advisory
  73. 2026-08-08 10:02 UTCGHSA enrichment
  74. 2026-08-08 05:50 UTCVendor advisory
  75. 2026-08-08 05:50 UTCGHSA enrichment

Publicly available exploits

(10 references)

Working exploit code is in the public domain (1 Metasploit module) (7 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/linux/local/cve_2026_43284_dirty_frag✓ verified
    First seen May 8, 2026

    xfrm-ESP Page-Cache Write via CVE-2026-43284

    Open source ↗
  • GitHub PoCankitrawatgit/DirtyFrag-Android-Root-Jailbreak
    First seen Oct 2, 2026

    DirtyFrag Android Root is an Android app and helper module chain based on DirtyFrag (CVE-2026-43284). Tested on iQOO Z9 5G.

    Open source ↗
  • GitHub PoCcoey0814/DirtyFrag-Galaxy
    First seen Sep 28, 2026

    One-click temporary KernelSU root (late-load) for Samsung Galaxy via DirtyFrag (CVE-2026-43284). No Shizuku/PC/ADB.

    Open source ↗
  • GitHub PoCa2333c/DFRoot
    First seen Sep 27, 2026

    三星 Galaxy S25 Ultra(SM-S938B)适配版 DFRoot:开机自动获取 root(DirtyFrag CVE-2026-43284 + CVE-2026-43499 双链路),全中文界面,fork 自 diabl0w/DFRoot

    Open source ↗
  • GitHub PoClukeslp/redtail-ioc
    First seen Jul 7, 2026

    IOCs and a read-only triage checklist from a real Linux root compromise: RedTail miner, XorDDoS persistence, MoneroOcean miner, DirtyFrag LPE (CVE-2026-43284/43500). CC0.

    Open source ↗
  • Exploit-DBEDB-52591
    First seen May 29, 2026

    Linux Kernel - Local Privilege Escalation

    Open source ↗
  • Exploit-DBEDB-52585
    First seen May 27, 2026

    Linux Kernel - Local Privilege Escalation

    Open source ↗
  • GitHub PoCjayhutajulu1/CVE-2026-43284-DirtyFrag-PoC
    First seen May 26, 2026

    Proof-of-concept for CVE-2026-43284 — 4-byte XFRM/ESP page-cache write primitive to patch a setuid binary (x86_64, user namespaces). Includes kernel preflight + SUID scan.

    Open source ↗
  • GitHub PoCkuniyal08/Dirty-Frag-CVE-2026-43284
    First seen May 19, 2026

    A report on Dirty Frag, which is a Linux Local Privilege Escalation (LPE) vulnerability chain that allows an unprivileged user to gain root access

    Open source ↗
  • GitHub PoCliamromanis101/DirtyFrag-Detector
    First seen May 11, 2026

    CVE-2026-43284/CVE-2026-43500 'DirtyFrag' Benign patch & mitigation detection script

    Open source ↗

Frequently asked(5)

What is CVE-2026-43284?
CVE-2026-43284 is a critical vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb frags MSGSPLICEPAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFLSHAREDFRAG after skbsplicefrom_iter(), so later paths that may modify packet data…
When was CVE-2026-43284 disclosed?
CVE-2026-43284 was first published on May 8, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43284 actively exploited?
CVE-2026-43284 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 2.5% probability of exploitation in the next 30 days (83rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43284?
CVE-2026-43284 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2026-43284?
A fix for CVE-2026-43284 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43284 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43284

Explore →

Is Your Infrastructure Affected by CVE-2026-43284?

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