drm/amdkfd: Validate CRIU-restored IDs before idr_alloc
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 40e8a766a761f7fdc8530347527b344fddf6f1a8 · < 85043dd49c2f51a37b22618168e3ae59ab92f0d6| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s AMD KFD CRIU restore flow does not validate userspace-provided object IDs before passing them to idr_alloc(). A local user able to submit restore data can supply an ID above INT_MAX, triggering a kernel warning that may cause a panic or reboot if panic_on_warn is enabled. Authentication requirements are not specified.
Operators running the Linux kernel with AMD KFD CRIU restore support should check their kernel versions; affected versions are not specified.