In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: check num_entries in GEM_OP GET_MAPPING_INFO… (CVE-2026-63878)
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.
AI Analysis
Technical 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).
Potential 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.
Mitigation Recommendations
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.
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: check num_entries in GEM_OP GET_MAPPING_INFO… (CVE-2026-63878)
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
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).
Potential 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.
Mitigation Recommendations
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.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-7q2q-cf6q-6c84
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63878"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ac2a4a8d59891302d8
Added to database: 07/19/2026, 19:38:20 UTC
Last enriched: 07/19/2026, 20:13:16 UTC
Last updated: 07/20/2026, 08:00:48 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.