VulnerabilityPublished 19 Jul 2026

CVE-2026-63878: Linux kernel · drm/amdgpu: check num_entries in GEM_OP GET_MAPPING_INFO

Source GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 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-7q2q-cf6q-6c84

What to do

AI-suggested

A fix has been applied in the Linux kernel source by adding a size bounds check on num_entries before allocation. Users should update their Linux kernel to a version that includes this fix. Since this is a kernel vulnerability, patching the kernel is the recommended mitigation. No other specific mitigations are indicated.

Description

A vulnerability in the Linux kernel's AMDGPU driver allowed an unbounded user-supplied value to be used in a memory allocation, potentially causing a kernel warning and panic on certain configurations. The issue was fixed by adding a size bounds check to reject oversized allocation requests early.

Impact

Exploitation of this vulnerability could cause a kernel warning and potentially a kernel panic on affected systems, leading to denial of service. There is no indication of code execution or privilege escalation. Systems with CONFIG_PANIC_ON_WARN=y are particularly affected as they will panic on the warning triggered by the oversized allocation.

Summary

The Linux kernel AMDGPU driver contained a vulnerability where the user-supplied num_entries parameter was used directly in a kvcalloc call without an upper bounds check. Because num_entries is a 32-bit unsigned integer and the allocation size could exceed INT_MAX, this could trigger a kernel warning and panic on systems configured with CONFIG_PANIC_ON_WARN=y. The fix involved adding a size bounds check before the allocation to reject excessively large num_entries values with an error code (-EINVAL).

References

Community reviews

Loading reviews…