CVE-2026-80870
Last modified
CVE-2026-80870 is a vulnerability of currently unknown severity. 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..
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 Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 40e8a766a761f7fdc8530347527b344fddf6f1a8, < f8687018f24037056692c1e93c7d96cc72889d5b; >= 40e8a766a761f7fdc8530347527b344fddf6f1a8, < 89a75e3349c4fae28cbedc711bc924cbc6293da2; >= 40e8a766a761f7fdc8530347527b344fddf6f1a8, < 085ea93bda71fee600cc12a17026598eb10dd1f9; >= 40e8a766a761f7fdc8530347527b344fddf6f1a8, < 543ed0f61d56501cc585162da600bbedd7c08c0f; >= 40e8a766a761f7fdc8530347527b344fddf6f1a8, < cb6311f25a096621ac7ffd91b50d1bb1cfb63a96; >= 40e8a766a761f7fdc8530347527b344fddf6f1a8, < 85043dd49c2f51a37b22618168e3ae59ab92f0d6 |
| Linux | Linux | 5.18 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-80870?
How severe is CVE-2026-80870?
How do I fix CVE-2026-80870?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-80865In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80866In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80867In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80868In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80869In the Linux kernel, the following vulnerability has been re…
- CVE-2026-8087A security flaw has been discovered in OSGeo gdal up to 3.13…7.8
- CVE-2026-80871In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80872In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80873In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80874In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80875In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80876In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-80870?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
