CVE-2026-80870

drm/amdkfd: Validate CRIU-restored IDs before idr_alloc

Published Sep 4, 2026 CVSS n/a EPSS < 1% KEV · Not listed

Description

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.

Affected Products

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

Linux

unaffected

Version	Status	Constraints
`40e8a766a761f7fdc8530347527b344fddf6f1a8`	affected	< f8687018f24037056692c1e93c7d96cc72889d5b
`40e8a766a761f7fdc8530347527b344fddf6f1a8`	affected	< 89a75e3349c4fae28cbedc711bc924cbc6293da2
`40e8a766a761f7fdc8530347527b344fddf6f1a8`	affected	< 085ea93bda71fee600cc12a17026598eb10dd1f9
`40e8a766a761f7fdc8530347527b344fddf6f1a8`	affected	< 543ed0f61d56501cc585162da600bbedd7c08c0f
`40e8a766a761f7fdc8530347527b344fddf6f1a8`	affected	< cb6311f25a096621ac7ffd91b50d1bb1cfb63a96
`40e8a766a761f7fdc8530347527b344fddf6f1a8`	affected	< 85043dd49c2f51a37b22618168e3ae59ab92f0d6

Linux

affected

Version	Status	Constraints
`5.18`	affected	—
`0`	unaffected	< 5.18
`6.1.178`	unaffected	≤ 6.1.*
`6.6.145`	unaffected	≤ 6.6.*
`6.12.97`	unaffected	≤ 6.12.*
`6.18.40`	unaffected	≤ 6.18.*
`7.1.5`	unaffected	≤ 7.1.*
`7.2`	unaffected	≤ *

No data.

Vendor Product Versions

Linux

Linux Kernel

Version	Status	Scheme	Platform
`[40e8a766a761f7fdc8530347527b344fddf6f1a8,f8687018f24037056692c1e93c7d96cc72889d5b)`	affected	code_commit	—
`[40e8a766a761f7fdc8530347527b344fddf6f1a8,89a75e3349c4fae28cbedc711bc924cbc6293da2)`	affected	code_commit	—
`[40e8a766a761f7fdc8530347527b344fddf6f1a8,085ea93bda71fee600cc12a17026598eb10dd1f9)`	affected	code_commit	—
`[40e8a766a761f7fdc8530347527b344fddf6f1a8,543ed0f61d56501cc585162da600bbedd7c08c0f)`	affected	code_commit	—
`[40e8a766a761f7fdc8530347527b344fddf6f1a8,cb6311f25a096621ac7ffd91b50d1bb1cfb63a96)`	affected	code_commit	—
`[40e8a766a761f7fdc8530347527b344fddf6f1a8,85043dd49c2f51a37b22618168e3ae59ab92f0d6)`	affected	code_commit	—

Linux

Linux Kernel

Version	Status	Scheme	Platform
`5.18`	affected	generic	—
`[0,5.18)`	unaffected	generic	—
`[6.1.178,6.1.*]`	unaffected	generic	—
`[6.6.145,6.6.*]`	unaffected	generic	—
`[6.12.97,6.12.*]`	unaffected	generic	—
`[6.18.40,6.18.*]`	unaffected	generic	—
`[7.1.5,7.1.*]`	unaffected	generic	—
`[7.2,*]`	unaffected	generic	—

Remediation

No solution or workaround provided in the CVE record

Tracking

Advisories

Source	ID	Title
Ubuntu USN	USN-8887-1	Linux kernel vulnerabilities
Ubuntu USN	USN-8888-1	Linux kernel (Azure) vulnerabilities
Ubuntu USN	USN-8889-1	Linux kernel (OEM) vulnerabilities
Ubuntu USN	USN-8887-2	Linux kernel (AWS) vulnerabilities
Ubuntu USN	USN-8888-2	Linux kernel (Azure) vulnerabilities
Ubuntu USN	USN-8887-3	Linux kernel vulnerabilities
Ubuntu USN	USN-8917-1	Linux kernel vulnerabilities
Ubuntu USN	USN-8918-1	Linux kernel (Azure) vulnerabilities
Ubuntu USN	USN-9003-1	Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN	USN-9024-1	Linux kernel vulnerabilities
Ubuntu USN	USN-9025-1	Linux kernel vulnerabilities
Ubuntu USN	USN-9026-1	Linux kernel (Azure) vulnerabilities
Ubuntu USN	USN-9040-1	Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN	USN-9043-1	Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN	USN-9066-1	Linux kernel (HWE) vulnerabilities
Ubuntu USN	USN-9091-1	Linux kernel (NVIDIA Tegra) vulnerabilities

Metrics

No CVSS v4.0

No CVSS v3.1

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Exploit prediction score: < 1% (0.215% probability within 30 days)

Key SSVC decision points have not yet been added.

References

Link	Providers
https://git.kernel.org/stable/c/085ea93bda71fee600cc12a17026598eb10dd1f9
https://git.kernel.org/stable/c/543ed0f61d56501cc585162da600bbedd7c08c0f
https://git.kernel.org/stable/c/85043dd49c2f51a37b22618168e3ae59ab92f0d6
https://git.kernel.org/stable/c/89a75e3349c4fae28cbedc711bc924cbc6293da2
https://git.kernel.org/stable/c/cb6311f25a096621ac7ffd91b50d1bb1cfb63a96
https://git.kernel.org/stable/c/f8687018f24037056692c1e93c7d96cc72889d5b

History

Sep 4, 2026 8:15 PM Weaknesses updated View changes

Type	Values Removed	Values Added
Weaknesses		CWE-20

Sep 4, 2026 5:00 PM Description updated. Title updated. First appearance in the feed. Affected versions updated. Affected vendors updated. Added references View changes

Type	Values Removed	Values Added
Description		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.
Title		drm/amdkfd: Validate CRIU-restored IDs before idr_alloc
First Time appeared		Linux Linux linux Kernel
CPEs		cpe:2.3:o:linux:linux_kernel::::::::
Vendors & Products		Linux Linux linux Kernel
References		https://git.kernel.org/stable/c/085ea93bda71fee600cc12a17026598eb10dd1f9 https://git.kernel.org/stable/c/543ed0f61d56501cc585162da600bbedd7c08c0f https://git.kernel.org/stable/c/85043dd49c2f51a37b22618168e3ae59ab92f0d6 https://git.kernel.org/stable/c/89a75e3349c4fae28cbedc711bc924cbc6293da2 https://git.kernel.org/stable/c/cb6311f25a096621ac7ffd91b50d1bb1cfb63a96 https://git.kernel.org/stable/c/f8687018f24037056692c1e93c7d96cc72889d5b