CVE-2026-63878
Last modified
CVE-2026-63878 is a vulnerability of currently unknown severity. 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). EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
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)
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 4d82724f7f2b847eb0454b1aab5450545b39abd4, < f059b4c493df3e54fe3ffe4658009c31864275da; >= 4d82724f7f2b847eb0454b1aab5450545b39abd4, < 967a00b8e06a7734aded23861faba9ee2462be87; >= 4d82724f7f2b847eb0454b1aab5450545b39abd4, < a1ba4594232c87c3b8defd6f89a2e40f8b08395d |
| Linux | Linux | 6.18 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-63878?
How severe is CVE-2026-63878?
How do I fix CVE-2026-63878?
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-63872Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-63873In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63874In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63875In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63876In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63877In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63879In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-6388A flaw was found in ArgoCD Image Updater. This vulnerability…9.1
- CVE-2026-63880In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63881In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63882In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63883In the Linux kernel, the following vulnerability has been re…7.3
Are you affected by CVE-2026-63878?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
