{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.190-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.113-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.2.9-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry  In a case where skb with an unconfirmed ct entry gets cloned, we may end up committing both 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 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 committing both clones without modifications into the same zone is needed.  So, let's just reset the entry in case for some reason we got an skb with a shared one during commit.  This doesn't affect any known use cases, but avoids any potential problems with sharing and modification of the unconfirmed ct entry.  The fixes tag points to the introduction of helpers, since that's the main UAF trigger for the sharing.",
  "id": "DEBIAN-CVE-2026-98491",
  "modified": "2026-10-19T04:47:39.042434349Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-98491"
    }
  ],
  "upstream": [
    "CVE-2026-98491"
  ]
}