Description
In the Linux kernel, the following vulnerability has been resolved:

net/sched: act_ct: avoid modifying shared unconfirmed ct entry

In a case where skb with an unconfirmed ct entry gets cloned, we may
end up processing both again but with different sets of extensions.

The series of events:

1. The first clone wants to commit and runs the helpers wiring up
the extension pointer into the expectation list.
2. Then it looses the confirmation keeping the entry unconfirmed.
3. Second clone now wants to commit labels or run NAT and adds the
new extension for that breaking the pointer in the expectation
list causing UAF on the destruction path later.

While this is possible to trigger, there should be no practical
network pipeline where we need to process both clones without
modifications in the same zone. So, let's just reset the entry in
case for some reason we got an skb with a shared one. This doesn't
affect any known use cases, but avoids any potential problems with
sharing and modification of the unconfirmed ct entry.

Unlike openvswitch module, act_ct allows for NAT without commit.
Changing that would be a uAPI break. So, act_ct needs to reset on NAT
regardless of the commit flag to avoid reallocation of the extension
space. This, however, doesn't really change the picture for sensible
networking cases as there should be no need to run the same packet
twice (before and after the clone) through conntrack without packet
header or zone changes and without commit.

The fixes tag points to the introduction of helpers, since that's the
main UAF trigger for the sharing.
Published: 2026-10-18
Score: n/a
EPSS: n/a
KEV: No
Impact: Use‑After‑Free leading to kernel memory corruption that could cause a crash or privilege escalation
Action: Patch immediately
AI Analysis

Impact

The vulnerability is a use‑after‑free in the Linux kernel’s conntrack action (act_ct). When an unconfirmed conntrack entry is cloned, both clones may modify the shared extension pointer, leaving one clone with a dangling pointer that can be accessed during cleanup. This can lead to memory corruption, kernel panic, or, in theory, elevation of privileges if an attacker can control the packet processing flow.

Affected Systems

It impacts all systems running the Linux kernel with the act_ct conntrack action module enabled. No specific kernel versions are listed, so any kernel that has not yet incorporated the patch to reset unconfirmed entries after cloning may be vulnerable.

Risk and Exploitability

No CVSS score, EPSS, or CISA KEV listing is provided, indicating limited public exploitation data. The exploit requires injecting cloned packets into the conntrack path, which is uncommon in normal network traffic but could be achievable in specialized or misconfigured environments. Given the patch already exists in the kernel source, the current risk is considered low to moderate until an attacker reliably triggers the VUAF path.

Generated by OpenCVE AI on October 18, 2026 at 16:24 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade your Linux kernel to a version that includes the act_ct reset patch
  • Reload the act_ct module after the kernel update to ensure the new logic is active
  • Monitor the network stack for unexpected crashes or kernel panics that could indicate misuse of conntrack entries

Generated by OpenCVE AI on October 18, 2026 at 16:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 18 Oct 2026 16:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-758

Sun, 18 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: net/sched: act_ct: avoid modifying shared unconfirmed ct entry In a case where skb with an unconfirmed ct entry gets cloned, we may end up processing both again but with different sets of extensions. The series of events: 1. The first clone wants to commit and runs the helpers wiring up the extension pointer into the expectation list. 2. Then it looses the confirmation keeping the entry unconfirmed. 3. Second clone now wants to commit labels or run NAT and adds the new extension for that breaking the pointer in the expectation list causing UAF on the destruction path later. While this is possible to trigger, there should be no practical network pipeline where we need to process both clones without modifications in the same zone. So, let's just reset the entry in case for some reason we got an skb with a shared one. This doesn't affect any known use cases, but avoids any potential problems with sharing and modification of the unconfirmed ct entry. Unlike openvswitch module, act_ct allows for NAT without commit. Changing that would be a uAPI break. So, act_ct needs to reset on NAT regardless of the commit flag to avoid reallocation of the extension space. This, however, doesn't really change the picture for sensible networking cases as there should be no need to run the same packet twice (before and after the clone) through conntrack without packet header or zone changes and without commit. The fixes tag points to the introduction of helpers, since that's the main UAF trigger for the sharing.
Title net/sched: act_ct: avoid modifying shared unconfirmed ct entry
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-18T15:14:51.664Z

Reserved: 2026-09-25T10:25:14.349Z

Link: CVE-2026-98441

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-18T16:16:54.393

Modified: 2026-10-18T16:16:54.393

Link: CVE-2026-98441

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-18T16:30:13Z

Weaknesses
  • CWE-758

    Reliance on Undefined, Unspecified, or Implementation-Defined Behavior