CVE-2026-46323

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH 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 — 4 sources updated this week
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

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(high)
EPSS
2.9%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 30, 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

Vendor Advisories for CVE-2026-46323(6)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-07-06ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-06ubuntu
ubuntulinux-tools-azure-7.0 (7.0.0-1007.7) @ resolute2026-07-06ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-07-06ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-07-06ubuntu
redhatkernel-0:5.14.0-570.123.1.el9_62026-06-22redhat
redhatkernel-0:6.12.0-55.82.1.el10_02026-06-22redhat
redhatkernel-0:5.14.0-427.132.1.el9_42026-06-22redhat

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(1)

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

Additional Vendor Advisories

(5)

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 40× in last 7d / 146× 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 146 total refreshes for this CVE.

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

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 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-46323 actively exploited?
CVE-2026-46323 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.

Start Free Scan →Browse All CVEs