CyberSecBulletin
CVE-2026-46323NVD status: Modified

Linux: Use After Free

CVE-2026-46323 is a high-severity use after free vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 3c6cc9f2ca65b6dd61b1af75452dc0e1cd0aad8d, 1f9c828556416fbe3f49386708ce999fc4d4da06, 479084ae0e1d9cb7929cb4298d35623de189f80a as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.14% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 3c6cc9f2ca65b6dd61b1af75452dc0e1cd0aad8d or 1f9c828556416fbe3f49386708ce999fc4d4da06 or 479084ae0e1d9cb7929cb4298d35623de189f80a or e334cbf3388fd9334503a778a82d9e9f14dd2f71, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.1.176 or 6.6.142 or 6.12.92 or 6.18.34, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux753f1ca4e1e50248a1b760c9774d6d6b354562cc up to, but not including, 3c6cc9f2ca65b6dd61b1af75452dc0e1cd0aad8d; 753f1ca4e1e50248a1b760c9774d6d6b354562cc up to, but not including, 1f9c828556416fbe3f49386708ce999fc4d4da06; 753f1ca4e1e50248a1b760c9774d6d6b354562cc up to, but not including, 479084ae0e1d9cb7929cb4298d35623de189f80a; 753f1ca4e1e50248a1b760c9774d6d6b354562cc up to, but not including, e334cbf3388fd9334503a778a82d9e9f14dd2f71; 753f1ca4e1e50248a1b760c9774d6d6b354562cc up to, but not including, 44bea2032af0425e4ce6d26a8af0ede79db49ec1; 753f1ca4e1e50248a1b760c9774d6d6b354562cc up to, but not including, 4db79a322db8c97f7b73b8a347395ef4d685eb40; 6.03c6cc9f2ca65b6dd61b1af75452dc0e1cd0aad8d, 1f9c828556416fbe3f49386708ce999fc4d4da06, 479084ae0e1d9cb7929cb4298d35623de189f80a, e334cbf3388fd9334503a778a82d9e9f14dd2f71, 44bea2032af0425e4ce6d26a8af0ede79db49ec1, 4db79a322db8c97f7b73b8a347395ef4d685eb40
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 10.0 Extended Update SupportNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9.4 Update Services for SAP SolutionsNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9.6 Extended Update SupportNot specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.17Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.18Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.19Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.20Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.21Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 6Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 7Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux for NVIDIA 26Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4Not specified in the recordNot stated
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)V3.1.6 and later; V3.1.7 and laterNot stated
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)V3.1.6 and later; V3.1.7 and laterNot stated
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)V3.1.6 and later; V3.1.7 and laterNot stated
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)V3.1.6 and later; V3.1.7 and laterNot stated
SiemensSIMATIC S7-1500 TM MFP - GNU/Linux subsystemall versionsNot stated
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)V3.1.6 and later; V3.1.7 and laterNot stated
LinuxLinux Kernel6.0 up to, but not including, 6.1.176; 6.2 up to, but not including, 6.6.142; 6.7 up to, but not including, 6.12.92; 6.13 up to, but not including, 6.18.34; 6.19 up to, but not including, 7.0.11; 7.16.1.176, 6.6.142, 6.12.92, 6.18.34, 7.0.11

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.8HighCNA

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

How developers prevent this class of flaw

  • Choose a language that provides automatic memory management.
  • When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.

More Use After Free vulnerabilities (CWE-416)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Use After Free vulnerabilities

Spotted an error? Tell us.