CVE-2026-63884

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. The CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

drm/i915: Fix potential UAF in TTM object purge

TLDR: The bo->ttm object might be changed by calling ttm_bo_validate(), move casting it to an i915_tt object later to actually get the right pointer.

A user reported hitting the following bug under heavy use on DG2:

[26620.095550] Oops: general protection fault, probably for non-canonical address 0xa56b6b6b6b6b6b8b: 0000 1 SMP NOPTI [26620.095556] CPU: 2 UID: 0 PID: 631 Comm: Xorg Not tainted 6.18.8 #1 PREEMPT(lazy) [26620.095558] Hardware name: ASRock B850M Steel Legend WiFi/B850M Steel Legend WiFi, BIOS 3.50 09/18/2025 [26620.095559] RIP: 0010:i915_ttm_purge+0x84/0x100 [i915] [26620.095604] Code: 00 00 00 48 8d 54 24 10 48 89 e6 48 89 fb e8 83 aa ae ff 85 c0 75 6f 48 83 bb a8 01 00 00 00 74 2c 48 8b 45 78 48 85 c0 74 23 <48> 8b 78 20 48 c7 c2 ff ff ff ff 31 f6 e8 7a 73 e3 e0 48 8b 7d 78 [26620.095605] RSP: 0018:ffffc90005fd7430 EFLAGS: 00010282 [26620.095607] RAX: a56b6b6b6b6b6b6b RBX: ffff8881f46c3dc0 RCX: 0000000000000000 [26620.095608] RDX: 0000000000000000 RSI: 0000000000000246 RDI: 00000000ffffffff [26620.095609] RBP: ffff888289610f00 R08: 0000000000000001 R09: ffff88823b022000 [26620.095609] R10: ffff888103029b28 R11: ffff8881fc7f3800 R12: ffff88810b6150d0 [26620.095609] R13: ffff888289610f00 R14: 0000000000000000 R15: ffff8881f46c3dc0 [26620.095610] FS: 00007f1004d86900(0000) GS:ffff88901c858000(0000) knlGS:0000000000000000 [26620.095611] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [26620.095611] CR2: 00007f0fdf489000 CR3: 000000035b0c1000 CR4: 0000000000750ef0 [26620.095612] PKRU: 55555554 [26620.095612] Call Trace: [26620.095615] [26620.095615] i915_ttm_move+0x2b9/0x420 [i915] [26620.095642] ? ttm_tt_init+0x65/0x80 [ttm] [26620.095644] ? i915_ttm_tt_create+0xc6/0x150 [i915] [26620.095667] ttm_bo_handle_move_mem+0xb6/0x160 [ttm] [26620.095669] ttm_bo_evict+0x100/0x150 [ttm] [26620.095671] ? preempt_count_add+0x64/0xa0 [26620.095673] ? _raw_spin_lock+0xe/0x30 [26620.095675] ? _raw_spin_unlock+0xd/0x30 [26620.095675] ? i915_gem_object_evictable+0xb7/0xd0 [i915] [26620.095704] ttm_bo_evict_cb+0x6e/0xd0 [ttm] [26620.095705] ttm_lru_walk_for_evict+0xa6/0x200 [ttm] [26620.095708] ttm_bo_alloc_resource+0x185/0x4f0 [ttm] [26620.095709] ? init_object+0x62/0xd0 [26620.095712] ttm_bo_validate+0x7a/0x180 [ttm] [26620.095713] ? _raw_spin_unlock_irqrestore+0x16/0x30 [26620.095714] __i915_ttm_get_pages+0xb0/0x170 [i915] [26620.095737] i915_ttm_get_pages+0x9f/0x150 [i915] [26620.095759] ? i915_gem_do_execbuffer+0xedc/0x2b40 [i915] [26620.095786] ? alloc_debug_processing+0xd0/0x100 [26620.095787] ? _raw_spin_unlock_irqrestore+0x16/0x30 [26620.095788] ? i915_vma_instance+0xa0/0x4e0 [i915] [26620.095822] __i915_gem_object_get_pages+0x2f/0x40 [i915] [26620.095848] i915_vma_pin_ww+0x706/0x980 [i915] [26620.095875] ? i915_gem_do_execbuffer+0xedc/0x2b40 [i915] [26620.095904] eb_validate_vmas+0x170/0xa00 [i915] [26620.095930] i915_gem_do_execbuffer+0x1201/0x2b40 [i915] [26620.095953] ? alloc_debug_processing+0xd0/0x100 [26620.095954] ? _raw_spin_unlock_irqrestore+0x16/0x30 [26620.095955] ? i915_gem_execbuffer2_ioctl+0xc9/0x240 [i915] [26620.095977] ? __wake_up_sync_key+0x32/0x50 [26620.095979] ? i915_gem_execbuffer2_ioctl+0xc9/0x240 [i915] [26620.096001] ? __slab_alloc.isra.0+0x67/0xc0 [26620.096003] i915_gem_execbuffer2_ioctl+0x11a/0x240 [i915]

Results from decode_stacktrace.sh pointed to dereference of a file pointer field of a i915 TTM page vector container associated with an object being purged on eviction. That path is taken when the object is marked as no longer needed.

Code analysis revealed a possibility of the i915 TTM page vector container being replaced with a new instance inside a function that purges content of the object, should it be still busy. That function is called, indirectly via a more general function that changes the object's placement and caching policy, ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Jul 21, 2026
Patch available.
Web page

drm/i915: Fix potential UAF in TTM object purge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/df73f3bc731af1c39ac5405bc59c4e7c6f8e9117
Web page

drm/i915: Fix potential UAF in TTM object purge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c9ae7e7e3bc98615364313b08d7acea5239ded0b
Web page

drm/i915: Fix potential UAF in TTM object purge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a29654d451bbffe63d584a4cf64ad0efce6bcf1c
Web page

drm/i915: Fix potential UAF in TTM object purge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5c4063c87a619e4df954c179d24628636f5db15f
Web page

drm/i915: Fix potential UAF in TTM object purge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28b22dbaf407598cb3bb1d2c586a6f8018690ac2
Web page

drm/i915: Fix potential UAF in TTM object purge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/073bcbc95e9648c976da1654c7590a8d6ee12c2d

Vendor Advisories for CVE-2026-63884(5)

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

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-10-01ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-01ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-01ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-01ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-01ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-10-01ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-01ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-01ubuntu
redhatkernel-0:5.14.0-687.41.1.el9_82026-08-20redhat
redhatkernel-0:6.12.0-211.49.1.el10_22026-08-20redhat
redhatkernel-0:4.18.0-553.156.1.el8_102026-08-17redhat
redhatkernel-rt-0:4.18.0-553.156.1.rt7.497.el8_102026-08-17redhat

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)
  • every version up to 7.0.12-1: fixed in 7.0.12-1
—

Additional Vendor Advisories

(8)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 14× in last 7d / 49× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 294 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 194 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-13 11:50 UTCEG score recompute
  3. 2026-10-13 11:50 UTCVendor advisory
  4. 2026-10-13 11:50 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-12 15:48 UTCEG score recompute
  7. 2026-10-11 19:33 UTCEG score recompute
  8. 2026-10-11 16:48 UTCEG score recompute
  9. 2026-10-11 14:09 UTCEG score recompute
  10. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-10-01 08:58 UTCEG score recompute
  22. 2026-10-01 08:58 UTCVendor advisory
  23. 2026-10-01 08:58 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 75 more
  1. 2026-09-28 07:34 UTCEG score recompute
  2. 2026-09-28 07:34 UTCVendor advisory
  3. 2026-09-28 07:34 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-09-24 04:15 UTCEG score recompute
  6. 2026-09-24 04:15 UTCVendor advisory
  7. 2026-09-24 04:15 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-09-23 02:11 UTCEG score recompute
  10. 2026-09-23 02:11 UTCVendor advisory
  11. 2026-09-23 02:11 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-09-18 04:24 UTCEG score recompute
  15. 2026-09-18 04:24 UTCVendor advisory
  16. 2026-09-18 04:24 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-09-17 10:00 UTCEG score recompute
  18. 2026-09-17 10:00 UTCVendor advisory
  19. 2026-09-17 10:00 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-09-16 13:08 UTCEG score recompute
  22. 2026-09-16 13:08 UTCVendor advisory
  23. 2026-09-16 13:07 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-09-14 05:06 UTCEG score recompute
  26. 2026-09-14 05:06 UTCVendor advisory
  27. 2026-09-14 05:06 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  28. 2026-09-13 16:20 UTCVendor advisory
  29. 2026-09-13 16:20 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  30. 2026-09-13 03:34 UTCEG score recompute
  31. 2026-09-13 03:34 UTCVendor advisory
  32. 2026-09-13 03:34 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  33. 2026-09-12 10:11 UTCVendor advisory
  34. 2026-09-12 10:11 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-09-11 19:41 UTCEG score recompute
  36. 2026-09-11 19:41 UTCVendor advisory
  37. 2026-09-11 19:41 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  39. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  40. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  41. 2026-09-07 23:38 UTCEG score recompute
  42. 2026-09-07 23:38 UTCVendor advisory
  43. 2026-09-07 23:37 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  45. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  46. 2026-09-06 13:04 UTCVendor advisory
  47. 2026-09-06 13:04 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-09-05 20:12 UTCEG score recompute
  49. 2026-09-05 20:12 UTCVendor advisory
  50. 2026-09-05 20:11 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  51. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  52. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  53. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  54. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  55. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  56. 2026-08-31 04:32 UTCEG score recompute
  57. 2026-08-31 04:32 UTCVendor advisory
  58. 2026-08-31 04:32 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  59. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  60. 2026-08-30 15:45 UTCVendor advisory
  61. 2026-08-30 15:45 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-08-30 02:59 UTCEG score recompute
  63. 2026-08-30 02:59 UTCVendor advisory
  64. 2026-08-30 02:59 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  66. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  67. 2026-08-28 02:05 UTCEG score recompute
  68. 2026-08-28 02:05 UTCVendor advisory
  69. 2026-08-28 02:05 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  71. 2026-08-27 13:16 UTCVendor advisory
  72. 2026-08-27 13:16 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-08-27 00:30 UTCEG score recompute
  74. 2026-08-27 00:30 UTCVendor advisory
  75. 2026-08-27 00:30 UTCGHSA enrichmentGHSA-8mf8-7jc8-gw2x · GitHub severity HIGH · GitHub CVSS 7.8

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-63884?
CVE-2026-63884 is a high-severity vulnerability; its CVE record was published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/i915: Fix potential UAF in TTM object purge TLDR: The bo->ttm object might be changed by calling ttmbovalidate(), move casting it to an i915_tt object later to actually get the right pointer. A user reported hitting the…
When was the CVE record for CVE-2026-63884 published?
The CVE record for CVE-2026-63884 was published on July 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2026-63884 actively exploited?
CVE-2026-63884 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63884?
CVE-2026-63884 has a CVSS base score of 7.8 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2026-63884?
A fix for CVE-2026-63884 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63884 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-63884?

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

Book a Demo →Browse All CVEs