CVE-2026-63878

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

A fix is available — apply it.

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)

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 27, 2026

Vendor Advisories for CVE-2026-63878(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 8× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 21:42 UTCEPSS rescore
  3. 2026-08-28 03:30 UTCVendor advisory
  4. 2026-08-28 03:30 UTCGHSA enrichment
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-25 06:45 UTCVendor advisory
  8. 2026-08-25 06:45 UTCGHSA enrichment
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 10:00 UTCVendor advisory
  11. 2026-08-22 10:00 UTCGHSA enrichment
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 13:33 UTCVendor advisory
  16. 2026-08-19 13:33 UTCGHSA enrichment
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-16 17:07 UTCVendor advisory
  20. 2026-08-16 17:07 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 20:40 UTCVendor advisory
  25. 2026-08-13 20:40 UTCGHSA enrichment
Show 49 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-11 00:11 UTCVendor advisory
  3. 2026-08-11 00:11 UTCGHSA enrichment
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-09 13:47 UTCEPSS rescore
  6. 2026-08-08 16:37 UTCEPSS rescore
  7. 2026-08-08 03:45 UTCVendor advisory
  8. 2026-08-08 03:45 UTCGHSA enrichment
  9. 2026-08-06 13:47 UTCEPSS rescore
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-05 07:18 UTCGHSA enrichment
  13. 2026-08-04 15:10 UTCEPSS rescore
  14. 2026-08-04 10:39 UTCEPSS rescore
  15. 2026-08-03 10:36 UTCEPSS rescore
  16. 2026-08-02 10:47 UTCVendor advisory
  17. 2026-08-02 10:47 UTCGHSA enrichment
  18. 2026-08-02 02:27 UTCEPSS rescore
  19. 2026-08-01 04:16 UTCEPSS rescore
  20. 2026-07-30 16:28 UTCEPSS rescore
  21. 2026-07-30 14:21 UTCEG score recompute
  22. 2026-07-30 14:20 UTCGHSA enrichment
  23. 2026-07-30 01:30 UTCEPSS rescore
  24. 2026-07-30 01:30 UTCEPSS rescore
  25. 2026-07-28 15:37 UTCEPSS rescore
  26. 2026-07-27 17:51 UTCGHSA enrichment
  27. 2026-07-27 14:14 UTCEPSS rescore
  28. 2026-07-26 14:54 UTCEPSS rescore
  29. 2026-07-26 14:54 UTCEPSS rescore
  30. 2026-07-26 11:02 UTCEG score recompute
  31. 2026-07-26 11:02 UTCVendor advisory
  32. 2026-07-26 11:02 UTCGHSA enrichment
  33. 2026-07-25 14:18 UTCEPSS rescore
  34. 2026-07-25 14:18 UTCEPSS rescore
  35. 2026-07-24 14:18 UTCEPSS rescore
  36. 2026-07-24 14:18 UTCEPSS rescore
  37. 2026-07-23 14:18 UTCEPSS rescore
  38. 2026-07-23 14:18 UTCEPSS rescore
  39. 2026-07-23 03:22 UTCEG score recompute
  40. 2026-07-22 14:08 UTCEPSS rescore
  41. 2026-07-22 14:08 UTCEPSS rescore
  42. 2026-07-21 15:25 UTCEPSS rescore
  43. 2026-07-21 15:25 UTCEPSS rescore
  44. 2026-07-20 17:39 UTCEG score recompute
  45. 2026-07-20 17:39 UTCGHSA enrichment
  46. 2026-07-20 17:08 UTCEPSS rescore
  47. 2026-07-19 17:49 UTCNVD update
  48. 2026-07-19 15:24 UTCEG score recompute
  49. 2026-07-19 15:19 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-63878?
CVE-2026-63878 is a publicly disclosed vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: check numentries in GEMOP GETMAPPINGINFO kvcalloc(args->numentries, sizeof(*vmentries), GFP_KERNEL) at amdgpugem.c:1050 uses the user-supplied numentries directly without any upper bounds check. Since numentries is a…
When was CVE-2026-63878 disclosed?
CVE-2026-63878 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63878 actively exploited?
CVE-2026-63878 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.3% of all scored CVEs.
How do I remediate CVE-2026-63878?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63878, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63878

Explore →

Is Your Infrastructure Affected by CVE-2026-63878?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.