CVE-2026-63878·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: check num_entries in GEM_OP GET_MAPPING_INFO kvcalloc(args->num_entries, sizeof(*vm_entries), GFP_KERNEL) at amdgpu_gem.c:1050 uses the user-supplied num_entries directly without any upper bounds check. Since num_entries is a __u32 and sizeof(drm_amdgpu_gem_vm_entry) is 32 bytes, a large num_entries produces an allocation exceeding INT_MAX, triggering WARNING in __kvmalloc_node_noprof(), causing a kernel WARNING, TAINT_WARN, and panic on CONFIG_PANIC_ON_WARN=y systems. Add a size bounds check before we invoke the kvzalloc() to reject oversized num_entries early with -EINVAL. (cherry picked from commit 1fe7bf5457f6efd7be60b17e23163ba54341d73d)
- Severity
- medium
- Software
- Kernel
- Fixed in
- 7.0.12
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.21% — higher than 11% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 6.19
Until: 7.0.12
Fixed in: 7.0.12
How to fix this CVE
Update your Linux kernel to version 7.0.12 or later to patch the memory allocation vulnerability in the AMD GPU driver's GEM_OP GET_MAPPING_INFO handler. The fix adds proper bounds validation for user-supplied allocation sizes, preventing excessive kernel memory requests that could trigger system warnings or panics. Systems running kernels 6.19 through 7.0.11 should prioritize this update.
sudo dnf update kernel && sudo rebootDefensia detects this vulnerability
How to check if you are affected
- Run 'uname -r' to display the currently running kernel version and confirm if it falls within the 6.19 to 7.0.11 range
- Check if AMD GPU drivers are loaded by running 'lsmod | grep amdgpu' or 'modprobe -l | grep amdgpu'
- Search kernel logs for memory allocation warnings using 'dmesg | grep -i kvmalloc' or 'journalctl -b | grep -i kvmalloc' to identify exploitation attempts
- After applying patches, verify the new kernel version with 'uname -r' and confirm it reports 7.0.12 or later
FAQ
What is CVE-2026-63878?
This vulnerability exists in the AMD GPU (amdgpu) driver's GEM memory management interface, where the kernel fails to validate the size of user-requested memory allocations before processing, allowing local attackers to trigger excessive memory requests that cause kernel warnings or system panics on systems configured to panic on warnings.
Is CVE-2026-63878 being actively exploited?
No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available, though it remains a local denial-of-service risk.
What versions of Kernel are affected by CVE-2026-63878?
Linux kernel versions 6.19 through 7.0.11 are affected; version 7.0.12 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-63878?
Run 'uname -r' and check if the output shows a kernel version between 6.19 and 7.0.11; additionally verify AMD GPU support is enabled by running 'lsmod | grep amdgpu'.
Does Defensia detect CVE-2026-63878?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-63878 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-63878. Free for 1 server.
Get started free