7.8

CVE-2026-98441: net/sched: act_ct: avoid modifying shared unconfirmed ct entry

Received
AliasesDEBIAN-CVE-2026-98441UBUNTU-CVE-2026-98441
Published 18-10-2026Last modified 24-10-2026

Vulnerability summary

CVE-2026-98441 is a high (CVSS 7.8) vulnerability in linux. EPSS estimates a 0.13% chance of exploitation in the next 30 days, higher than 2.9% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 7.8, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
7.8/10
010
High · v3.1 (CVE.org)
EPSS score
0.13%
0%100%
Low · -0.04 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 17 · Related 16

Timeline

  1. 18-10-2026
    PublishedVulnerability first disclosed.
  2. 24-10-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

5 scores · 4 sources · 2 versions

EPSS trend

Probability

0.13%

Chance of exploitation in the next 30 days

Percentile

3%

Versus all other CVEs

30-day change

Decrease -0.04 pp

From 0.17% on 21-10-2026

21-10-202620-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu169 products
  • linuxAll versions (No fix recorded) | < 6.8.0-149.149 | < 7.0.0-42.42
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 6.8.0-1069.74 | < 7.0.0-1016.17
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian2 products
  • linux< 6.12.113-1 | < 7.2.9-1
  • linux-6.12< 6.12.113-1~deb12u1
Linux1 product
  • linux≥ a21b06e7319129994f339ed47f512bbe57b77f5b, < c812bb4aea13d385d048b5b24756aee2edf6f99e | ≥ a21b06e7319129994f339ed47f512bbe57b77f5b, < 2b783c562c3238ff50c34fd7a72a735c9cc73d9a | ≥ a21b06e7319129994f339ed47f512bbe57b77f5b, < 4a04ed91575819fb1859311113e95700b709bec7 | ≥ a21b06e7319129994f339ed47f512bbe57b77f5b, < b097d9d7a5b09c8ec5c4c1a08e35ac5a66b06b44 | ≥ a21b06e7319129994f339ed47f512bbe57b77f5b, < f85009dfcd65e5969526b0db7a49b5413746e630 | 6.2

3 vendors · 172 products

References

23 links
Show all 23 references