{
  "affected": [
    {
      "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:  perf/x86/intel/uncore: Fix uncore_box ref/unref ordering  In uncore_event_cpu_online(), uncore_box_ref() was called before uncore_change_context().  uncore_box_ref() gates on box-\u003ecpu \u003e= 0, but box-\u003ecpu is still -1 at that point because uncore_change_context() has not run yet.  As a result, the box is never initialized on the first CPU to come online in a die, leaving it permanently uninitialized in the single-CPU-per-die case.  Thus, box-\u003erefcnt is one count below the true value, and in the CPU offline path, the box will be torn down on the second-to-last CPU.  In uncore_event_cpu_offline(), uncore_box_unref() was called after uncore_change_context(), so box-\u003ecpu is already -1 when the collector CPU goes offline, which prevents it from tearing down the box.  Fix by swapping the call order in both paths so that uncore_box_{ref,unref}() runs at the point where box-\u003ecpu reflects the correct context.  Move allocate_boxes() out of uncore_box_ref() to enable this reordering.",
  "id": "DEBIAN-CVE-2026-93181",
  "modified": "2026-09-18T04:47:26.277577891Z",
  "published": "2026-09-17T17:18:14.027Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-93181"
    }
  ],
  "upstream": [
    "CVE-2026-93181"
  ]
}