HIGH Introduced in 6.2
netfilter Conntrack UAF
CVE-2026-98441
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
KernelScan AI7.0HIGH
01Description
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.
02KernelScan AI Analysis
Risk summary
A local user with CAP_NET_ADMIN can trigger a use-after-free in the conntrack subsystem by cloning packets with unconfirmed connection tracking entries and processing them through tc actions with commit or NAT operations. This leads to kernel memory corruption, enabling privilege escalation or denial of service.
Vulnerability analysis
When a network packet with an unconfirmed connection tracking entry is cloned (e.g., via tc mirred or other cloning actions), both clones can be processed through the act_ct action. If the first clone commits the connection, it wires extension pointers into the expectation list, but then loses confirmation. The second clone, attempting to commit labels or perform NAT, adds new extensions that corrupt the shared expectation list pointers. On connection destruction, this results in a use-after-free. The fix detects shared unconfirmed entries before commit or NAT operations and resets the connection tracking state, forcing a fresh lookup. The vulnerability is reachable by any local user who can configure tc actions with commit or NAT (requiring CAP_NET_ADMIN), typically in container or multi-tenant environments where unprivileged users can manage traffic control rules.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 6.12 | 6.2 | 6.12.112 | 2b783c562c32 |
| 6.18 | 6.2 | 6.18.55 | 4a04ed915758 |
| 6.6 | 6.2 | 6.6.160 | c812bb4aea13 |
| 7.2 | 6.2 | 7.2.9 | b097d9d7a5b0 |
| mainline | 6.2 | 7.3 | f85009dfcd65 |
| cip/6.12 | 6.2 | 6.12.112-cip33 | 2b783c562c32 |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Fixed in 6.12.112-cip33 |