CVE-2026-46323: net: gro: don't merge zcopy skbs

Published May 19, 2026
·
Updated

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 SKBFLMANAGEDFRAGREFS flag.

When SKBFLMANAGEDFRAGREFS 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 Software

11 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.141.1-1<6.6.143.1-1
6.6.143.1-1
Linux Linux kernel>=6.0<6.1.176
Linux Linux kernel>=6.2<6.6.142
Linux Linux kernel>=6.7<6.12.92
Linux Linux kernel>=6.13<6.18.34
Linux Linux kernel>=6.19<7.0.11
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.143.1-1
  2. Configuration

    Ensure the GRO code uses the SKBFL_MANAGED_FRAG_REFS flag so that the skb doesn't hold a reference (per the resolved vulnerability behavior).

    Linux kernel GRO (net: gro) SKBFL_MANAGED_FRAG_REFS flag = set/enable
  3. Configuration

    Modify skb_gro_receive() / GRO frag-merge so that when either the last skb in the GRO chain (the skb you would append frags to) or the source skb is zerocopy, the skbs are not merged (to prevent UAF from un-fixed page refcounts on shinfo->frags).

    Linux kernel GRO (net: gro) GRO frag merging policy for zerocopy SKBs = do not merge zerocopy skbs / do not merge when last skb in GRO chain is zerocopy or when source skb is zerocopy

Event History

May 19, 2026
Data Sourced
via Red Hat·01:49 PM
DescriptionSeverityAffected Software
Jun 9, 2026
CVE Published
via MITRE·12:11 PM
Data Sourced
via MITRE·12:11 PM
DescriptionSeverity
Data Sourced
via NVD·01:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 10, 2026
Data Sourced
via Microsoft·08:06 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:06 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2026-46323?

CVE-2026-46323 has a risk score of 57, indicating a moderate severity level.

2

How do I fix CVE-2026-46323?

To remediate CVE-2026-46323, update the Linux kernel to the latest stable version that includes the security patch.

3

What systems are affected by CVE-2026-46323?

CVE-2026-46323 affects the Linux kernel, specifically versions that utilize the gro (Generic Receive Offload) feature.

4

What vulnerabilities are related to CVE-2026-46323?

CVE-2026-46323 can be related to other vulnerabilities in the Linux kernel that involve memory management and network packet handling.

5

What changes were made to resolve CVE-2026-46323?

The resolution for CVE-2026-46323 involves preventing the merging of zerocopy skbs in the skb_gro_receive() function without proper checks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203