{"id":"CVE-2026-80870","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      -\u003e create_signal_event() / create_other_event()\n          -\u003e allocate_event_notification_slot()\n              -\u003e idr_alloc(..., *restore_id, *restore_id + 1, ...)\n\nFor BO restore:\n\n  criu_restore_memory_of_gpu()\n      -\u003e idr_alloc(..., bo_priv-\u003eidr_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.","modified":"2026-09-06T03:47:00.950811983Z","published":"2026-09-04T16:48:31.902Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80870.json"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/085ea93bda71fee600cc12a17026598eb10dd1f9"},{"type":"WEB","url":"https://git.kernel.org/stable/c/543ed0f61d56501cc585162da600bbedd7c08c0f"},{"type":"WEB","url":"https://git.kernel.org/stable/c/85043dd49c2f51a37b22618168e3ae59ab92f0d6"},{"type":"WEB","url":"https://git.kernel.org/stable/c/89a75e3349c4fae28cbedc711bc924cbc6293da2"},{"type":"WEB","url":"https://git.kernel.org/stable/c/cb6311f25a096621ac7ffd91b50d1bb1cfb63a96"},{"type":"WEB","url":"https://git.kernel.org/stable/c/f8687018f24037056692c1e93c7d96cc72889d5b"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80870.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80870"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"40e8a766a761f7fdc8530347527b344fddf6f1a8"},{"fixed":"f8687018f24037056692c1e93c7d96cc72889d5b"},{"fixed":"89a75e3349c4fae28cbedc711bc924cbc6293da2"},{"fixed":"085ea93bda71fee600cc12a17026598eb10dd1f9"},{"fixed":"543ed0f61d56501cc585162da600bbedd7c08c0f"},{"fixed":"cb6311f25a096621ac7ffd91b50d1bb1cfb63a96"},{"fixed":"85043dd49c2f51a37b22618168e3ae59ab92f0d6"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80870.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.18.0"},{"fixed":"6.1.178"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.145"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.97"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.40"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.1.5"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80870.json"}}],"schema_version":"1.9.0"}