CVE-2026-46323

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

net: gro: don't merge zcopy skbs

skb_gro_receive() can currently copy frags between the source and GRO skb, without checking the zerocopy status, and in particular the SKBFL_MANAGED_FRAG_REFS flag.

When SKBFL_MANAGED_FRAG_REFS is set, the skb doesn't hold a reference on the pages in shinfo->frags. Appending those frags to another skb's frags without fixing up the page refcount can lead to UAF.

When either the last skb in the GRO chain (the one we would append frags to) or the source skb is zerocopy, don't merge the skbs.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (5)

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

net: gro: don't merge zcopy skbs - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: gro: don't merge zcopy skbs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4db79a322db8c97f7b73b8a347395ef4d685eb40
generic

net: gro: don't merge zcopy skbs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/479084ae0e1d9cb7929cb4298d35623de189f80a
generic

net: gro: don't merge zcopy skbs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/44bea2032af0425e4ce6d26a8af0ede79db49ec1
generic

net: gro: don't merge zcopy skbs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1f9c828556416fbe3f49386708ce999fc4d4da06

Patch Availability(11)

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

(6)

Data Freshness Timeline

(refreshed 16× in last 7d / 96× 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 156 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46323?
CVE-2026-46323 is a high vulnerability published on June 9, 2026. In the Linux kernel, the following vulnerability has been resolved: net: gro: don't merge zcopy skbs skbgroreceive() can currently copy frags between the source and GRO skb, without checking the zerocopy status, and in particular the SKBFLMANAGEDFRAG_REFS flag. When SKBFLMANAGEDFRAG_REFS is set,…
When was CVE-2026-46323 disclosed?
CVE-2026-46323 was first published in the National Vulnerability Database on June 9, 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-46323 actively exploited?
CVE-2026-46323 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.5% of all scored CVEs.
What is the CVSS score of CVE-2026-46323?
CVE-2026-46323 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46323?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46323, 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-46323

Explore →

Is Your Infrastructure Affected by CVE-2026-46323?

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