VulnerabilityPublished 4 Sep 2026Updated 9 Oct 2026

CVE-2026-80870: Linux kernel · drm/amdkfd: Validate CRIU-restored IDs before idr_alloc

Affects Linux kernelSource GCVE Database

Not known to be exploited · fixed in 7.0.0-1014.14~24.04.1 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.0.0-1014.14~24.04.1, 7.0.0-1017.17~24.04.1, 7.0.0-1016.16~24.04.1 +11

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-3fvv-ffr9-f4xf

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected <7.0.0-38.38	Fixed in 7.0.0-38.38
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected <7.0.0-1017.17	Fixed in 7.0.0-1017.17
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected <7.0.0-1016.16	Fixed in 7.0.0-1016.16
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected <7.0.0-1008.9	Fixed in 7.0.0-1008.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

An official patch is available that adds validation to ensure restored IDs do not exceed INT_MAX, preventing kernel warnings and potential panics. Users should apply the updated Linux kernel versions that include this fix. No additional mitigation steps are required beyond applying the official patch.

Description

A vulnerability in the Linux kernel's AMD KFD CRIU restore functionality allowed unchecked userspace-provided IDs to be passed to the idr_alloc() function. If these restored IDs exceeded the signed int limit, it could trigger a kernel warning (WARN), potentially causing a kernel panic or reboot on systems configured with panic_on_warn. The issue was fixed by adding validation to ensure restored IDs do not exceed INT_MAX, returning an error if invalid. This fix prevents invalid restore data from causing kernel warnings while preserving valid restore behavior.

Impact

If exploited, this vulnerability could cause the Linux kernel to emit warnings that may lead to a kernel panic or system reboot on systems with panic_on_warn enabled. This could result in denial of service due to unexpected system crashes. There is no indication of privilege escalation or data compromise from this vulnerability. No known exploits in the wild have been reported.

Summary

The Linux kernel's drm/amdkfd subsystem had a vulnerability in its CRIU restore flow where restored object IDs from userspace were not validated before being passed to idr_alloc(). Specifically, restored IDs larger than INT_MAX could trigger a WARN in the IDR layer, which is undesirable and may cause system panic or reboot on certain configurations. The flaw affected the functions kfd_criu_restore_event() and criu_restore_memory_of_gpu(). The patch added INT_MAX validation before using restored IDs, returning -EINVAL for invalid IDs to prevent kernel warnings and maintain valid restore functionality.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Oct 2026, 04:13 UTC

Technical details

References

Community reviews

Related threats