CVE-2026-46300

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-26. NVD baseline CVSS 7.8; sources differ by 0.0.

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

A fix is available — apply it.

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

net: skbuff: preserve shared-frag marker during coalescing

skb_try_coalesce() can attach paged frags from @from to @to. If @from has SKBFL_SHARED_FRAG set, the resulting @to skb can contain the same externally-owned or page-cache-backed frags, but the shared-frag marker is currently lost.

That breaks the invariant relied on by later in-place writers. In particular, ESP input checks skb_has_shared_frag() before deciding whether an uncloned nonlinear skb can skip skb_cow_data(). If TCP receive coalescing has moved shared frags into an unmarked skb, ESP can see skb_has_shared_frag() as false and decrypt in place over page-cache backed frags.

Propagate SKBFL_SHARED_FRAG when skb_try_coalesce() transfers paged frags. The tailroom copy path does not need the marker because it copies bytes into @to's linear data rather than transferring frag descriptors.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

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
Severity78% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
83%
KEV
Not listed

Published

May 23, 2026

Last Modified

July 23, 2026

Advisory Details (10)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

oss-security - Linux kernel: Dirty Frag variants — fix merged into netdev

http://www.openwall.com/lists/oss-security/2026/05/21/11
generic

oss-security - Re: Linux kernel LPE ("fragnesia", copyfail 3.0)

http://www.openwall.com/lists/oss-security/2026/05/13/5
generic

net: skbuff: preserve shared-frag marker during coalescing - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: skbuff: preserve shared-frag marker during coalescing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d3e5fd19fe1063bf607219e8562fbd567b8e8d5
generic

net: skbuff: preserve shared-frag marker during coalescing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78bf6b6bb19541d19fbda6242e7cfe2c682763c0
generic

net: skbuff: preserve shared-frag marker during coalescing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/760e1addc27ba1a7beb4a0a7e8b3e9ec49e7a34e
generic

net: skbuff: preserve shared-frag marker during coalescing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3bd9e113d50034db99d7ef69fd8e5242d15e414a
generic

net: skbuff: preserve shared-frag marker during coalescing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3884358a9286b17f389a72b1426fc4547c23c111
generic

net: skbuff: preserve shared-frag marker during coalescing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3599e6b3cc1ada96883d496a50a210d3afbb6987
generic

net: skbuff: preserve shared-frag marker during coalescing - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-46300(20)

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

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhcos-417.94.202606250942-02026-07-09redhat
redhatrhcos-414.92.202606231112-02026-07-01redhat
redhatkernel-0:6.12.0-231.12.el10nv2026-06-30redhat
redhatrhcos-416.94.202606051757-02026-06-18redhat
redhatrhcos-415.92.202606030318-02026-06-11redhat
redhatrhcos-4.21.9.6.202606030721-02026-06-11redhat
redhatrhcos-4.19.9.6.202606031700-02026-06-10redhat
redhatkpatch-patch2026-06-09redhat
redhatrhcos-412.86.202605271418-02026-06-04redhat
redhatrhcos-413.92.202605271328-02026-06-04redhat
redhatrhcos-418.94.202605260517-02026-06-03redhat
redhatrhcos-4.20.9.6.202605270908-02026-06-03redhat
redhatrhcos-416.94.202605200242-02026-05-29redhat
redhatkernel-0:5.14.0-284.172.1.el9_22026-05-26redhat
redhatopenshift-0:4.21.0-202605142021.p2.geab2218.assembly.stream.el102026-05-26redhat
redhatkernel-0:5.14.0-427.126.1.el9_42026-05-21redhat
redhatkernel-0:4.18.0-305.192.1.el8_42026-05-21redhat
redhatkernel-0:4.18.0-372.193.1.el8_62026-05-21redhat
redhatkernel-0:6.12.0-55.75.1.el10_02026-05-21redhat
redhatkernel-0:5.14.0-570.116.1.el9_62026-05-21redhat
redhatkernel-0:5.14.0-687.10.1.el9_82026-05-20redhat
redhatkernel-0:4.18.0-553.125.1.el8_102026-05-20redhat
redhatkernel-0:6.12.0-211.16.1.el10_22026-05-20redhat
redhatkernel-0:4.18.0-477.143.1.el8_82026-05-20redhat
redhatkernel-0:6.12.0-211.8.el10nv2026-05-20redhat
redhatkernel-rt-0:4.18.0-553.125.1.rt7.466.el8_102026-05-20redhat
linuxKernel @ 5.10.257—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.

Weakness Classification(2)

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

Additional Vendor Advisories

(15)

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 12× in last 7d / 46× 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 166 total refreshes for this CVE.

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

Publicly available exploits

(5 references)

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

  • GitHub PoCazilRababe/CVE-2026-46300
    First seen Jun 22, 2026

    Technical analysis of CVE-2026-46300 (Fragnesia), a Linux kernel page-cache write vulnerability that enables local privilege escalation through SKBFL_SHARED_FRAG invariant violations in the networking stack.

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

    Linux Kernel - Local Privilege Escalation

    Open source ↗
  • GitHub PoCKoshmare-Blossom/Fragnesia-go
    First seen May 20, 2026

    A Go implementation of fragnesia (CVE-2026-46300)

    Open source ↗
  • GitHub PoC0xBlackash/CVE-2026-46300
    First seen May 15, 2026

    CVE-2026-46300

    Open source ↗
  • GitHub PoCHORKimhab/CVE-2026-46300
    First seen May 14, 2026

    CVE-2026-46300

    Open source ↗

Frequently asked(5)

What is CVE-2026-46300?
CVE-2026-46300 is a high vulnerability published on May 23, 2026. In the Linux kernel, the following vulnerability has been resolved: net: skbuff: preserve shared-frag marker during coalescing skbtrycoalesce() can attach paged frags from @from to @to. If @from has SKBFLSHAREDFRAG set, the resulting @to skb can contain the same externally-owned or…
When was CVE-2026-46300 disclosed?
CVE-2026-46300 was first published in the National Vulnerability Database on May 23, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46300 actively exploited?
CVE-2026-46300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 17.0% of all scored CVEs.
What is the CVSS score of CVE-2026-46300?
CVE-2026-46300 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46300, 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-46300

Explore →

Is Your Infrastructure Affected by CVE-2026-46300?

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

Start Free Scan →Browse All CVEs