CVE-2026-80870

CVE CVE-2026-80870EUVD EUVD-2026-71500Published 2026-09-04T16:48:31.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Validate CRIU-restored IDs before idr_alloc The KFD CRIU restore flow restores previously saved object IDs from userspace. For event restore: kfd_criu_restore_event() -> create_signal_event() / create_other_event() -> allocate_event_notification_slot() -> idr_alloc(..., *restore_id, *restore_id + 1, ...) For BO restore: criu_restore_memory_of_gpu() -> idr_alloc(..., bo_priv->idr_handle, ...) In both cases, the restored ID comes from userspace-provided CRIU data. idr_alloc() expects the ID range values to fit within signed int limits. If a restored ID is larger than INT_MAX, it can trigger a WARN in the IDR layer. A kernel WARN is undesirable because it prints a warning trace and may cause a panic or reboot on systems with panic_on_warn enabled. Smatch reported these paths as allowing unchecked userspace values to reach idr_alloc(). Add INT_MAX validation before using restored IDs in: - kfd_criu_restore_event() - criu_restore_memory_of_gpu() If the restored ID is invalid, return -EINVAL. This prevents invalid restore data from reaching the IDR layer and avoids WARN-triggering paths, while keeping valid restore behavior unchanged.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 6.6.145; patch: 7.1.5; patch: 6.18.40; 40e8a766a761f7fdc8530347527b344fddf6f1a8 <085ea93bda71fee600cc12a17026598eb10dd1f9; 40e8a766a761f7fdc8530347527b344fddf6f1a8 <85043dd49c2f51a37b22618168e3ae59ab92f0d6; 40e8a766a761f7fdc8530347527b344fddf6f1a8 <cb6311f25a096621ac7ffd91b50d1bb1cfb63a96; patch: 6.1.178; 40e8a766a761f7fdc8530347527b344fddf6f1a8 <89a75e3349c4fae28cbedc711bc924cbc6293da2; 40e8a766a761f7fdc8530347527b344fddf6f1a8 <f8687018f24037056692c1e93c7d96cc72889d5b; patch: 0; 5.18; 40e8a766a761f7fdc8530347527b344fddf6f1a8 <543ed0f61d56501cc585162da600bbedd7c08c0f; patch: 7.2; patch: 6.12.97

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.