CVE-2026-46323 remediation guide

Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support

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.

Open CVE record

ProductLinux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support

Affected versions>= 753f1ca4e1e50248a1b760c9774d6d6b354562cc < 3c6cc9f2ca65b6dd61b1af75452dc0e1cd0aad8d, >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc < 1f9c828556416fbe3f49386708ce999fc4d4da06, >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc < 479084ae0e1d9cb7929cb4298d35623de189f80a, >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc < e334cbf3388fd9334503a778a82d9e9f14dd2f71, >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc < 44bea2032af0425e4ce6d26a8af0ede79db49ec1, >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc < 4db79a322db8c97f7b73b8a347395ef4d685eb40, >= 6.0, >= 6.0 < 6.1.176, >= 6.2 < 6.6.142, >= 6.7 < 6.12.92, >= 6.13 < 6.18.34, >= 6.19 < 7.0.11, 7.1

Fixed versions6.1.176, 6.6.142, 6.12.92, 6.18.34, 7.0.11

Priority basisReview · CVSS 7.8 · EPSS 0.14%

Identify the affected asset

Confirm whether Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc < 3c6cc9f2ca65b6dd61b1af75452dc0e1cd0aad8d, >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc < 1f9c828556416fbe3f49386708ce999fc4d4da06, >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc < 479084ae0e1d9cb7929cb4298d35623de189f80a, >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc < e334cbf3388fd9334503a778a82d9e9f14dd2f71, >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc < 44bea2032af0425e4ce6d26a8af0ede79db49ec1, >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc < 4db79a322db8c97f7b73b8a347395ef4d685eb40, >= 6.0, >= 6.0 < 6.1.176, >= 6.2 < 6.6.142, >= 6.7 < 6.12.92, >= 6.13 < 6.18.34, >= 6.19 < 7.0.11, 7.1. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 6.1.176, 6.6.142, 6.12.92, 6.18.34, 7.0.11. Preserve configuration and rollback material before change.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.