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 — 4 sources updated 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

August 7, 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(12)

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

Patch Availability(16)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-20ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-08-20ubuntu
ubuntulinux-tools-azure-7.0 (7.0.0-1007.7) @ resolute2026-08-20ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-20ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-08-20ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-08-20ubuntu
redhatrhcos-417.94.202607240132-02026-08-06redhat
redhatrhcos-418.94.202607211754-02026-07-29redhat
redhatrhcos-4.19.9.6.202607220857-02026-07-29redhat
redhatrhcos-4.20.9.6.202607221038-02026-07-28redhat
redhatrhcos-4.21.9.6.202607221317-02026-07-28redhat
redhatkernel-0:6.12.0-211.38.1.el10_22026-07-23redhat
redhatkernel-0:5.14.0-687.22.1.el9_82026-07-06redhat
redhatkernel-0:5.14.0-427.132.1.el9_42026-06-22redhat
redhatkernel-0:5.14.0-570.123.1.el9_62026-06-22redhat
redhatkernel-0:6.12.0-55.82.1.el10_02026-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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (139 versions)7.0.12-1—

Weakness Classification(2)

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

Additional Vendor Advisories

(6)

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 29× in last 7d / 154× 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 296 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 August 7, 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.4% 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

See which npm, PyPI, Go, and Maven packages are affected by 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