{
  "cveId": "CVE-2026-63878",
  "url": "https://patchblox.com/security/cve/CVE-2026-63878",
  "summary": "CVE-2026-63878 is fixed in linux on 1 platform by DEBIAN-CVE-2026-63878 (version 7.0.12-1), released July 20, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: check num_entries in GEM_OP GET_MAPP...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: check num_entries in GEM_OP GET_MAPPING_INFO  kvcalloc(args-\u003Enum_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)",
  "published": "2026-07-19T16:17:04Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.0016,
  "epssPercentile": 0.05206,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.0.12-1",
      "fix": "DEBIAN-CVE-2026-63878",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-63878",
      "released": "2026-07-20T12:58:36Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-10T01:44:33Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}