CVE-2026-46323

net: gro: don't merge zcopy skbs

HIGH
7.8
CVSS Score
Published: June 9, 2026 at 12:11 PM UTC
Updated: October 19, 2026 at 08:18 PM UTC
6 products affected across 3 vendorsLinux KernelOpenShift Container PlatformSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.0 ≤ v < 6.1.1766.13 ≤ v < 6.18.346.19 ≤ v < 7.0.116.2 ≤ v < 6.6.1426.7 ≤ v < 6.12.927.17.1 rc17.1 rc27.1 rc37.1 rc4753f1ca4e1e50248a1b760c9774d6d6b354562cc
Vendor states this is fixed in 1f9c828556416fbe3f49386708ce999fc4d4da06 (fixed)
Vendor states this is fixed in 3c6cc9f2ca65b6dd61b1af75452dc0e1cd0aad8d (fixed)
Vendor states this is fixed in 44bea2032af0425e4ce6d26a8af0ede79db49ec1 (fixed)
Vendor states this is fixed in 479084ae0e1d9cb7929cb4298d35623de189f80a (fixed)
Vendor states this is fixed in 4db79a322db8c97f7b73b8a347395ef4d685eb40 (fixed)
Vendor states this is fixed in e334cbf3388fd9334503a778a82d9e9f14dd2f71 (fixed)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.92 (unaffected)
Vendor states this is fixed in 6.18.34 (unaffected)
Vendor states this is fixed in 6.6.142 (unaffected)
Vendor states this is fixed in 7.0.11 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)
Vendor states this is fixed in 4.19.9.6.202607220857-0 (unaffected)
Vendor states this is fixed in 4.20.9.6.202607221038-0 (unaffected)
Vendor states this is fixed in 4.21.9.6.202607221317-0 (unaffected)
Vendor states this is fixed in 417.94.202607240132-0 (unaffected)
Vendor states this is fixed in 418.94.202607211754-0 (unaffected)
Vendor states this is fixed in 0:5.14.0-427.132.1.el9_4 (unaffected)
Vendor states this is fixed in 0:5.14.0-570.123.1.el9_6 (unaffected)
Vendor states this is fixed in 0:5.14.0-687.22.1.el9_8 (unaffected)
Vendor states this is fixed in 0:6.12.0-211.38.1.el10_2 (unaffected)
Vendor states this is fixed in 0:6.12.0-55.82.1.el10_0 (unaffected)
Vendor states this is fixed in 6 (unaffected)
Vendor states this is fixed in 7 (unaffected)
Vendor states this is fixed in 8 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-123CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card