{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-80870",
  "modified": "2026-10-07T17:22:01Z",
  "upstream": [
    "CVE-2026-80870"
  ],
  "published": "2026-09-04T16:49:36Z",
  "summary": "drm/amdkfd: Validate CRIU-restored IDs before idr_alloc",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdkfd: Validate CRIU-restored IDs before idr_alloc\n\nThe KFD CRIU restore flow restores previously saved object IDs from\nuserspace.\n\nFor event restore:\n\n  kfd_criu_restore_event()\n      -> create_signal_event() / create_other_event()\n          -> allocate_event_notification_slot()\n              -> idr_alloc(..., *restore_id, *restore_id + 1, ...)\n\nFor BO restore:\n\n  criu_restore_memory_of_gpu()\n      -> idr_alloc(..., bo_priv->idr_handle, ...)\n\nIn both cases, the restored ID comes from userspace-provided CRIU data.\n\nidr_alloc() expects the ID range values to fit within signed int\nlimits. If a restored ID is larger than INT_MAX, it can trigger a WARN\nin the IDR layer.\n\nA kernel WARN is undesirable because it prints a warning trace and may\ncause a panic or reboot on systems with panic_on_warn enabled.\n\nSmatch reported these paths as allowing unchecked userspace values to\nreach idr_alloc().\n\nAdd INT_MAX validation before using restored IDs in:\n\n- kfd_criu_restore_event()\n- criu_restore_memory_of_gpu()\n\nIf the restored ID is invalid, return -EINVAL.\n\nThis prevents invalid restore data from reaching the IDR layer and\navoids WARN-triggering paths, while keeping valid restore behavior\nunchanged.",
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.178",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-80870"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/f8687018f24037056692c1e93c7d96cc72889d5b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/89a75e3349c4fae28cbedc711bc924cbc6293da2"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/085ea93bda71fee600cc12a17026598eb10dd1f9"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/543ed0f61d56501cc585162da600bbedd7c08c0f"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/cb6311f25a096621ac7ffd91b50d1bb1cfb63a96"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/85043dd49c2f51a37b22618168e3ae59ab92f0d6"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-09-04T16:49:36Z"
  }
}