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
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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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%
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

Published

June 9, 2026

Last Modified

September 8, 2026

Advisory Details (5)

Auto-updated Jun 14, 2026
Patch available.
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(18)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-09-14ubuntu
ubuntulinux-tools-azure-7.0 (7.0.0-1007.7) @ resolute2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-09-14ubuntu
redhatkpatch-patch2026-09-02redhat
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.21.9.6.202607221317-02026-07-28redhat
redhatrhcos-4.20.9.6.202607221038-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:6.12.0-55.82.1.el10_02026-06-22redhat
redhatkernel-0:5.14.0-427.132.1.el9_42026-06-22redhat
redhatkernel-0:5.14.0-570.123.1.el9_62026-06-22redhat
linuxKernel @ 6.1.176 (fixes >=6.0.0)—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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)
  • every version up to 7.0.12-1: fixed in 7.0.12-1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 5× in last 7d / 30× 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 373 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-03 10:09 UTCOSV refresh
  4. 2026-10-01 19:50 UTCEPSS rescore
  5. 2026-09-30 15:03 UTCEPSS rescore
  6. 2026-09-28 13:51 UTCEPSS rescore
  7. 2026-09-27 13:48 UTCEPSS rescore
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-23 17:53 UTCEPSS rescore
  10. 2026-09-20 20:15 UTCEPSS rescore
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-17 19:31 UTCEPSS rescore
  13. 2026-09-16 14:08 UTCEPSS rescore
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-14 04:38 UTCEG score recompute
  16. 2026-09-14 04:38 UTCVendor advisory
  17. 2026-09-14 04:38 UTCGHSA enrichment
  18. 2026-09-13 16:47 UTCEPSS rescore
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 09:37 UTCEPSS rescore
  21. 2026-09-10 09:34 UTCEPSS rescore
  22. 2026-09-08 22:00 UTCEPSS rescore
  23. 2026-09-08 09:44 UTCEG score recompute
  24. 2026-09-08 09:44 UTCVendor advisory
  25. 2026-09-08 09:44 UTCGHSA enrichment
Show 75 more
  1. 2026-09-08 08:59 UTCEG score recompute
  2. 2026-09-08 08:59 UTCVendor advisory
  3. 2026-09-08 08:59 UTCGHSA enrichment
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-03 13:19 UTCEG score recompute
  8. 2026-09-03 13:19 UTCVendor advisory
  9. 2026-09-03 13:19 UTCGHSA enrichment
  10. 2026-09-03 12:27 UTCEG score recompute
  11. 2026-09-03 12:27 UTCVendor advisory
  12. 2026-09-03 12:26 UTCGHSA enrichment
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-09-01 13:44 UTCEG score recompute
  15. 2026-09-01 13:44 UTCVendor advisory
  16. 2026-09-01 13:44 UTCGHSA enrichment
  17. 2026-09-01 12:19 UTCEG score recompute
  18. 2026-09-01 12:19 UTCVendor advisory
  19. 2026-09-01 12:19 UTCGHSA enrichment
  20. 2026-08-31 00:56 UTCEG score recompute
  21. 2026-08-31 00:56 UTCVendor advisory
  22. 2026-08-31 00:56 UTCGHSA enrichment
  23. 2026-08-30 19:17 UTCEPSS rescore
  24. 2026-08-30 01:22 UTCEPSS rescore
  25. 2026-08-28 21:41 UTCEPSS rescore
  26. 2026-08-27 14:25 UTCEPSS rescore
  27. 2026-08-26 14:46 UTCEPSS rescore
  28. 2026-08-25 13:49 UTCEPSS rescore
  29. 2026-08-25 12:19 UTCEG score recompute
  30. 2026-08-25 12:19 UTCVendor advisory
  31. 2026-08-25 12:18 UTCGHSA enrichment
  32. 2026-08-25 00:52 UTCEG score recompute
  33. 2026-08-25 00:52 UTCVendor advisory
  34. 2026-08-25 00:52 UTCGHSA enrichment
  35. 2026-08-24 13:29 UTCEG score recompute
  36. 2026-08-24 13:29 UTCVendor advisory
  37. 2026-08-24 13:29 UTCGHSA enrichment
  38. 2026-08-24 12:22 UTCEG score recompute
  39. 2026-08-24 12:22 UTCVendor advisory
  40. 2026-08-24 12:22 UTCGHSA enrichment
  41. 2026-08-23 23:42 UTCVendor advisory
  42. 2026-08-23 23:41 UTCGHSA enrichment
  43. 2026-08-23 11:17 UTCEG score recompute
  44. 2026-08-23 11:17 UTCVendor advisory
  45. 2026-08-23 11:17 UTCGHSA enrichment
  46. 2026-08-23 00:19 UTCEPSS rescore
  47. 2026-08-21 23:49 UTCEPSS rescore
  48. 2026-08-21 19:47 UTCVendor advisory
  49. 2026-08-21 19:47 UTCGHSA enrichment
  50. 2026-08-21 08:16 UTCEG score recompute
  51. 2026-08-21 08:16 UTCVendor advisory
  52. 2026-08-21 08:16 UTCGHSA enrichment
  53. 2026-08-20 22:55 UTCEPSS rescore
  54. 2026-08-20 20:51 UTCVendor advisory
  55. 2026-08-20 20:51 UTCGHSA enrichment
  56. 2026-08-20 09:20 UTCEG score recompute
  57. 2026-08-20 09:20 UTCVendor advisory
  58. 2026-08-20 09:20 UTCGHSA enrichment
  59. 2026-08-19 17:04 UTCEPSS rescore
  60. 2026-08-18 13:48 UTCEPSS rescore
  61. 2026-08-17 13:47 UTCEPSS rescore
  62. 2026-08-17 12:35 UTCVendor advisory
  63. 2026-08-17 12:35 UTCGHSA enrichment
  64. 2026-08-17 00:52 UTCEG score recompute
  65. 2026-08-17 00:52 UTCVendor advisory
  66. 2026-08-17 00:52 UTCGHSA enrichment
  67. 2026-08-16 14:56 UTCEPSS rescore
  68. 2026-08-16 11:55 UTCEG score recompute
  69. 2026-08-16 11:55 UTCVendor advisory
  70. 2026-08-16 11:55 UTCGHSA enrichment
  71. 2026-08-16 02:14 UTCEPSS rescore
  72. 2026-08-16 00:40 UTCVendor advisory
  73. 2026-08-16 00:40 UTCGHSA enrichment
  74. 2026-08-15 11:35 UTCEG score recompute
  75. 2026-08-15 11:35 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 on June 9, 2026, with the most recent update on September 8, 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.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46323?
CVE-2026-46323 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46323?
A fix for CVE-2026-46323 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46323 are linked in the Vendor Advisories panel on this page.

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.