{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-72449",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-72449"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdkfd: fix list_del corruption in kfd_criu_resume_svm\n\nThe cleanup tail of kfd_criu_resume_svm() walks\nsvms->criu_svm_metadata_list and kfree()s each struct criu_svm_metadata\nwithout removing it from the list. The list head is left pointing at\nfreed kmalloc-96 objects.\n\nA second AMDKFD_IOC_CRIU_OP from the same process re-enters: list_empty()\nreads the dangling ->next (use-after-free), the loop walks freed entries,\nand each is kfree()'d again (double-free). This is reachable by an\nunprivileged render-group user via /dev/kfd with no capabilities required.\n\nAdd list_del() before the kfree() so the list is properly emptied. The\nlist_for_each_entry_safe() iterator already caches the next pointer, so\nunlinking during the walk is safe.\n\n(cherry picked from commit 6322d278a298e2c1430b9d2697743d3a04b788b1)",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "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-72449"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c8a8d350a273c005a48c64c4519d21b2a51c5ceb"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/506e635aed05dbdeef11e3c59f6e42980cda5b6d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/838b57b3e7ce8cce0fda56d0861add3d464dd6c8"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/96ac562a9ea3020981f536384711190841c81aa8"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/e33a3bd5cb8d0cf1557dee014115f812c9686130"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8fa5655da368d0306c03e9dc9cda8ae2a7840926"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-17T05:50:24Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The bug is reached only via the local AMDKFD_IOC_CRIU_OP ioctl on /dev/kfd (unlocked_ioctl -> kfd_ioctl_criu -> criu_resume -> kfd_criu_resume_svm); there is no network, adjacent-radio, or physical-device entry path.\nAC:L - An attacker who can open /dev/kfd controls the full CRIU restore/resume ioctl sequence and can deterministically trigger the bug by issuing KFD_CRIU_OP_RESUME twice after restore populates criu_svm_metadata_list; no uncontrollable race or rare layout is required.\nPR:L - The fix commit and ioctl path show exploitation by a local render-group user opening /dev/kfd; CAP_CHECKPOINT_RESTORE/SYS_ADMIN gates CRIU ioctls but are obtainable in a user namespace, matching basic local user privilege rather than init-namespace root only.\nUI:N - Exploitation requires only the attacker's own ioctl calls to /dev/kfd after CRIU restore; no victim click, mount, file open, or other interactive action is needed.\nS:U - Corruption is confined to kernel heap list metadata in amdkfd for the calling KFD process context; impact stays within the kernel security authority and does not cross a VM, IOMMU, or hypervisor boundary.\nC:H - After the first resume, list_empty() and list iteration dereference freed kmalloc-96 criu_svm_metadata objects (use-after-free reads of ->next/list pointers), enabling attacker-influenced heap disclosure beyond a bounded leak.\nI:H - A second resume walks the corrupted list and kfree()s the same objects again (double-free on kmalloc-96 slabs), a standard exploitable kernel heap primitive for arbitrary memory corruption and potential privilege escalation.\nA:H - The use-after-free and double-free reliably corrupt kernel heap state and commonly cause BUG/KASAN faults, oops, or panic when the dangling list is traversed again, producing system-wide denial of service."
    }
  }
}