{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  bpf: Fix potential UAF in bpf_netns_link_update_prog  In bpf_netns_link_update_prog, the checks for old_prog and prog type are currently performed locklessly before acquiring netns_bpf_mutex. This creates a race condition that can lead to a UAF issue.  If two threads concurrently execute BPF_LINK_UPDATE on the same netns link, the following execution path can trigger a UAF:  CPU0                                          CPU1 bpf_netns_link_update_prog   if (old_prog \u0026\u0026 old_prog != link-\u003eprog)     return -EPERM;                                               bpf_netns_link_update_prog                                                 if (old_prog \u0026\u0026 old_prog != link-\u003eprog)                                                 ...                                                 old_prog = xchg(\u0026link-\u003eprog, new_prog);                                                 bpf_prog_put(old_prog);   if (new_prog-\u003etype != link-\u003eprog-\u003etype) \u003c-- trigger UAF  Fix this by moving the old_prog and prog-\u003etype checks inside the netns_bpf_mutex critical section. Meanwhile, use guard() to simplify lock management and avoid all the goto jumping.",
  "id": "DEBIAN-CVE-2026-90393",
  "modified": "2026-09-18T04:47:33.948262934Z",
  "published": "2026-09-17T17:17:38.903Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-90393"
    }
  ],
  "upstream": [
    "CVE-2026-90393"
  ]
}