{
  "id": "CVE-2026-98441",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-98441",
  "published_at": "2026-10-18T15:14:51.664Z",
  "title": "net/sched: act_ct: avoid modifying shared unconfirmed ct entry",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: act_ct: avoid modifying shared unconfirmed ct entry\n\nIn a case where skb with an unconfirmed ct entry gets cloned, we may\nend up processing both again but with different sets of extensions.\n\nThe series of events:\n\n 1. The first clone wants to commit and runs the helpers wiring up\n    the extension pointer into the expectation list.\n 2. Then it looses the confirmation keeping the entry unconfirmed.\n 3. Second clone now wants to commit labels or run NAT and adds the\n    new extension for that breaking the pointer in the expectation\n    list causing UAF on the destruction path later.\n\nWhile this is possible to trigger, there should be no practical\nnetwork pipeline where we need to process both clones without\nmodifications in the same zone.  So, let's just reset the entry in\ncase for some reason we got an skb with a shared one.  This doesn't\naffect any known use cases, but avoids any potential problems with\nsharing and modification of the unconfirmed ct entry.\n\nUnlike openvswitch module, act_ct allows for NAT without commit.\nChanging that would be a uAPI break.  So, act_ct needs to reset on NAT\nregardless of the commit flag to avoid reallocation of the extension\nspace.  This, however, doesn't really change the picture for sensible\nnetworking cases as there should be no need to run the same packet\ntwice (before and after the clone) through conntrack without packet\nheader or zone changes and without commit.\n\nThe fixes tag points to the introduction of helpers, since that's the\nmain UAF trigger for the sharing.",
  "cvss_by_source": {
    "cna": 7.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= a21b06e7319129994f339ed47f512bbe57b77f5b, \u003c c812bb4aea13d385d048b5b24756aee2edf6f99e",
          "\u003e= a21b06e7319129994f339ed47f512bbe57b77f5b, \u003c 2b783c562c3238ff50c34fd7a72a735c9cc73d9a",
          "\u003e= a21b06e7319129994f339ed47f512bbe57b77f5b, \u003c 4a04ed91575819fb1859311113e95700b709bec7",
          "\u003e= a21b06e7319129994f339ed47f512bbe57b77f5b, \u003c b097d9d7a5b09c8ec5c4c1a08e35ac5a66b06b44",
          "\u003e= a21b06e7319129994f339ed47f512bbe57b77f5b, \u003c f85009dfcd65e5969526b0db7a49b5413746e630"
        ],
        "fixed_in": [
          "c812bb4aea13d385d048b5b24756aee2edf6f99e",
          "2b783c562c3238ff50c34fd7a72a735c9cc73d9a",
          "4a04ed91575819fb1859311113e95700b709bec7",
          "b097d9d7a5b09c8ec5c4c1a08e35ac5a66b06b44",
          "f85009dfcd65e5969526b0db7a49b5413746e630"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "6.2"
        ],
        "fixed_in": [
          "0",
          "6.6.160",
          "6.12.112",
          "6.18.55",
          "7.2.9",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "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."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
