CVE-2026-43284

CRITICALPre-NVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than the CVSS score beside it.

Score elevated to 9.0 because EPSS predicted 99% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. 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 (continuous uplift above 30%)
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Weaponized

Also known asEUVD-2026-28535 (ENISA EUVD) · GHSA-mmw8-mxmc-8w2r (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 99%
  • Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 99%CVSS: 7.8Exploit: Metasploit · other public PoCExposed 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
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation99% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
99%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.8 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
99% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 8, 2026

Last Modified

November 11, 2026

Advisory Details (10)

Auto-updated May 11, 2026
Patch available.
Web page

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

https://git.kernel.org/stable/c/fe785bb3a8096dffcc4048a85cd0c83337eeecad
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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

https://git.kernel.org/stable/c/8253aab4659ca16116b522203c2a6b18dccacea7
Web page

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
Web page

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
Web page

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
Web page

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

Vendor and National Authority Advisories for CVE-2026-43284(20)

These vendors and national cybersecurity authorities published their own advisory mentioning this CVE — often with remediation steps + affected product lists not in NVD. An authority's is an excerpt, in the language it published it in, not translated, and credited to it with a link.

Patch Availability(25)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift/ose-rhel-coreos-9:417.94.202606250942-02026-07-09redhat
redhatkernel-0:6.12.0-231.12.el10nv2026-06-30redhat
redhatopenshift/ose-rhel-coreos-9:413.92.202606160406-02026-06-25redhat
redhatopenshift/ose-rhel-coreos-9:415.92.202606030318-02026-06-11redhat
redhatopenshift/ose-rhel-coreos-8: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:6.12.0-211.7.3.el10_22026-05-19redhat
redhatkernel-0:5.14.0-687.5.3.el9_82026-05-19redhat
redhatkernel-0:6.12.0-211.7.el10nv2026-05-15redhat
redhatopenshift/ose-rhel-coreos-8:412.86.202605111404-02026-05-14redhat
redhatopenshift/ose-rhel-coreos-9:414.92.202605111427-02026-05-14redhat
redhatopenshift/ose-rhel-coreos-9:416.94.202605101426-02026-05-13redhat
redhatopenshift/ose-rhel-coreos-9:4.19.9.6.202605110225-02026-05-13redhat
redhatopenshift/ose-rhel-coreos-9:418.94.202605101521-02026-05-13redhat
redhatopenshift/ose-rhel-coreos-9:4.21.9.6.202605110143-02026-05-13redhat
redhatopenshift/ose-rhel-coreos-9:4.20.9.6.202605110206-02026-05-13redhat
redhatkernel-0:5.14.0-570.113.1.el9_62026-05-13redhat
redhatkernel-0:4.18.0-553.124.1.el8_102026-05-12redhat
redhatkernel-rt-0:5.14.0-70.179.1.rt21.251.el9_02026-05-12redhat
redhatkernel-rt-0:4.18.0-553.124.1.rt7.465.el8_102026-05-12redhat
redhatkernel-0:6.12.0-55.73.1.el10_02026-05-12redhat
redhatkernel-rt-0:5.14.0-284.170.1.rt14.455.el9_22026-05-12redhat
linuxKernel @ 5.10.255 (fixes >=4.11.0)—osv

These rows come from Red Hat and OSV. 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

(22)

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 17× in last 7d / 69× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 408 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 308 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(22 references, 10 shown)

Public exploit code is referenced for this CVE (1 Metasploit module, 2 Exploit-DB entries, 14 GitHub PoCs), as are 5 GitHub checker repositories. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitexploit/linux/local/cve_2026_43284_dirty_frag✓ verified
    Published May 21, 2026

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

    Open source ↗
  • GitHub PoCnoctide/redmi-k50-temp-root
    Published Nov 7, 2026

    Redmi K50 (rubens) 临时 Root 教程 — 基于 DirtyFrag (CVE-2026-43284) + libbase fallback

    Open source ↗
  • GitHub PoCmcxiaochenn/iqooNeo8-V2301A-DirtyFrag
    Published Nov 4, 2026

    iQOO Neo8 (PD2301/V2301A) 一键越狱 — DirtyFrag (CVE-2026-43284) port on the pyb110 UI

    Open source ↗
  • GitHub PoCRemiPelloux/GalaxyCrash
    Published Oct 19, 2026

    Ephemeral root for Samsung Galaxy devices via CVE-2026-43284 — stability fork of DirtyFrag. Reboot to undo.

    Open source ↗
  • GitHub PoCankitrawatgit/DirtyFrag-Android-Root-Jailbreak
    Published 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 PoCa2333c/DFRoot
    Published 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
    Published 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
    Published May 29, 2026

    Linux Kernel - Local Privilege Escalation

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

    Linux Kernel - Local Privilege Escalation

    Open source ↗
  • GitHub PoCjayhutajulu1/CVE-2026-43284-DirtyFrag-PoC
    Published 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 ↗

Frequently asked(5)

What is CVE-2026-43284?
CVE-2026-43284 is a critical-severity vulnerability; its CVE record was 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 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…
When was the CVE record for CVE-2026-43284 published?
The CVE record for CVE-2026-43284 was published on May 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 11, 2026; the record at its source may have been updated since.
Is CVE-2026-43284 actively exploited?
CVE-2026-43284 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 99% probability of exploitation in the next 30 days (99th 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 CISA-ADP (Vulnrichment) CVSS v3.1 + 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 and National Authority Advisories panel on this page. NCSC-NL's 2 advisories for CVE-2026-43284 are also listed there, in Dutch, as NCSC-NL published it; not translated.

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.