CVE-2026-98441

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

  • High 7.8

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.

Key facts

Published
18 Oct 2026
Last changed
24 Oct 2026
Assigned by
Linux
EPSS
0.133% likely to be exploited in the next 30 days, higher than 2.94% of CVEs (scores for 18 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.8CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • a21b06e7319129994f339ed47f512bbe57b77f5b up to but excluding c812bb4aea13d385d048b5b24756aee2edf6f99e (affected)
  • a21b06e7319129994f339ed47f512bbe57b77f5b up to but excluding 2b783c562c3238ff50c34fd7a72a735c9cc73d9a (affected)
  • a21b06e7319129994f339ed47f512bbe57b77f5b up to but excluding 4a04ed91575819fb1859311113e95700b709bec7 (affected)
  • a21b06e7319129994f339ed47f512bbe57b77f5b up to but excluding b097d9d7a5b09c8ec5c4c1a08e35ac5a66b06b44 (affected)
  • a21b06e7319129994f339ed47f512bbe57b77f5b up to but excluding f85009dfcd65e5969526b0db7a49b5413746e630 (affected)
LinuxLinux
  • Default status: affected
  • 6.2 (affected)
  • 0 up to but excluding 6.2 (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.112 up to and including 6.12.* (unaffected)
  • 6.18.55 up to and including 6.18.* (unaffected)
  • 7.2.9 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References