PoC Monitor
← All CVEs
CVE-2026-98441published 18 Oct 2026 15:14 UTCData: JSON · API

Linux

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

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= a21b06e7319129994f339ed47f512bbe57b77f5b, < c812bb4aea13d385d048b5b24756aee2edf6f99e
  • >= a21b06e7319129994f339ed47f512bbe57b77f5b, < 2b783c562c3238ff50c34fd7a72a735c9cc73d9a
  • >= a21b06e7319129994f339ed47f512bbe57b77f5b, < 4a04ed91575819fb1859311113e95700b709bec7
  • >= a21b06e7319129994f339ed47f512bbe57b77f5b, < b097d9d7a5b09c8ec5c4c1a08e35ac5a66b06b44
  • >= a21b06e7319129994f339ed47f512bbe57b77f5b, < f85009dfcd65e5969526b0db7a49b5413746e630

Fixed in c812bb4aea13d385d048b5b24756aee2edf6f99e, 2b783c562c3238ff50c34fd7a72a735c9cc73d9a, 4a04ed91575819fb1859311113e95700b709bec7, b097d9d7a5b09c8ec5c4c1a08e35ac5a66b06b44, f85009dfcd65e5969526b0db7a49b5413746e630

Linux Linux
  • 6.2

Fixed in 0, 6.6.160, 6.12.112, 6.18.55, 7.2.9, 7.3

Mitigation

Upgrade Linux to c812bb4aea13d385d048b5b24756aee2edf6f99e or 2b783c562c3238ff50c34fd7a72a735c9cc73d9a or 4a04ed91575819fb1859311113e95700b709bec7 or b097d9d7a5b09c8ec5c4c1a08e35ac5a66b06b44 or f85009dfcd65e5969526b0db7a49b5413746e630 or later.

Upgrade Linux to 0 or 6.6.160 or 6.12.112 or 6.18.55 or 7.2.9 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published18 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.