{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.5-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  accel/amdxdna: reject user command submission without a command BO  amdxdna_drm_submit_execbuf() passes the user-supplied command BO handle straight into amdxdna_cmd_submit() with drv_cmd == NULL. When the handle is AMDXDNA_INVALID_BO_HANDLE (0), the block that fetches job-\u003ecmd_bo is skipped, leaving it NULL, and no check rejects it on the user path (the !job-\u003ecmd_bo guard lives inside the != INVALID branch).  The job is then armed and pushed to the DRM scheduler. aie2_sched_job_run() takes the drv_cmd == NULL path and calls amdxdna_cmd_set_state(job-\u003ecmd_bo) -\u003e amdxdna_gem_vmap(NULL) -\u003e to_gobj(NULL)-\u003edev, a NULL pointer dereference in the drm_sched worker. A process with access to the accel node on a system with a probed AMD NPU can trigger a kernel oops with a single AMDXDNA_EXEC_CMD ioctl (cmd_handles = 0).  Only internal driver commands (SYNC_DEBUG_BO / ATTACH_DEBUG_BO) legitimately pass AMDXDNA_INVALID_BO_HANDLE, and they always set drv_cmd. Reject the invalid handle for user submissions (drv_cmd == NULL) at the submit choke point so every user path is covered.  Found by 0sec automated security-research tooling (https://0sec.ai).",
  "id": "DEBIAN-CVE-2026-72091",
  "modified": "2026-08-17T08:47:38.199814059Z",
  "published": "2026-08-15T06:21:23.180Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-72091"
    }
  ],
  "upstream": [
    "CVE-2026-72091"
  ]
}