CVE-2026-89815

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

drm/ttm: Drop tt->restore after successful restore

ttm_pool_restore_and_alloc() can successfully complete the restore process via ttm_pool_restore_commit(), but tt->restore is not dropped afterward. As a result, subsequent backup/restore flows observe what appears to be a completed restore, while in reality shmem handles are still installed in tt->pages, leading to the stack trace below.

Fix this by freeing and dropping tt->restore in ttm_pool_restore_and_alloc() upon successful completion of the restore.

20545 [  309.784531] RIP: 0010:sg_alloc_append_table_from_pages+0x38c/0x490 20547 [  309.809570] RSP: 0018:ffffc9000623b838 EFLAGS: 00010206 20548 [  309.814827] RAX: 0000000000001000 RBX: ffff88816e42a160 RCX: 0000000000000000 20549 [  309.821986] RDX: 0000000000002000 RSI: 0000000000000003 RDI: 0000000000001000 20550 [  309.829147] RBP: ffff88816e42a168 R08: 0000000000000002 R09: 000000007ffff000 20551 [  309.836310] R10: ffffc9000623b928 R11: 0000000000000000 R12: 000000007ffff000 20552 [  309.843471] R13: ffff88815ba5a100 R14: 0000000000000000 R15: 0000000000000001 20553 [  309.850634] FS:  00007f9ff305e700(0000) GS:ffff888276c94000(0000) knlGS:0000000000000000 20554 [  309.858749] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 20555 [  309.864519] CR2: 00007f9fca701000 CR3: 00000001565e2005 CR4: 0000000008f70ef0 20556 [  309.871678] PKRU: 55555558 20557 [  309.874403] Call Trace: 20558 [  309.876866]  20559 [  309.878988]  sg_alloc_table_from_pages_segment+0x60/0x100 20560 [  309.884415]  ? ttm_resource_manager_usage+0x36/0x60 [ttm] 20561 [  309.889845]  ? xe_tt_map_sg+0x7d/0xd0 [xe] 20562 [  309.894045]  xe_tt_map_sg+0x7d/0xd0 [xe] 20563 [  309.898037]  xe_bo_move+0x927/0xaa0 [xe] 20564 [  309.902029]  ttm_bo_handle_move_mem+0xba/0x170 [ttm] 20565 [  309.907022]  ttm_bo_validate+0xbe/0x190 [ttm] 20566 [  309.911405]  xe_bo_validate+0x9a/0x120 [xe] 20567 [  309.915663]  xe_gpuvm_validate+0xd9/0x140 [xe] 20568 [  309.920206]  drm_gpuvm_validate+0x2f0/0x5b0 [drm_gpuvm] 20569 [  309.925459]  ? drm_exec_lock_obj+0x63/0x210 [drm_exec] 20570 [  309.930627]  xe_vm_validate_rebind+0x46/0xb0 [xe] 20571 [  309.935428]  xe_exec_fn+0x20/0x40 [xe] 20572 [  309.939249]  drm_gpuvm_exec_lock+0x78/0xc0 [drm_gpuvm] 20573 [  309.944410]  xe_validation_exec_lock+0x5a/0xa0 [xe] 20574 [  309.949385]  xe_exec_ioctl+0x806/0xc30 [xe] 20575 [  309.953639]  ? ttwu_queue_wakelist+0xd9/0xf0 20576 [  309.957935]  ? __pfx_xe_exec_fn+0x10/0x10 [xe] 20577 [  309.962449]  ? __wake_up_common+0x73/0xa0 20578 [  309.966482]  ? __pfx_xe_exec_ioctl+0x10/0x10 [xe] 20579 [  309.971263]  drm_ioctl_kernel+0xa3/0x100 20580 [  309.975209]  drm_ioctl+0x213/0x440 20581 [  309.978637]  ? __pfx_xe_exec_ioctl+0x10/0x10 [xe] 20582 [  309.983415]  xe_drm_ioctl+0x67/0xd0 [xe] 20583 [  309.987408]  __x64_sys_ioctl+0x7f/0xd0

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2026

Last Modified

September 21, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

drm/ttm: Drop tt->restore after successful restore - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a46ab76b6cf5478e2ac7b942a377c7a1827b436a
generic

drm/ttm: Drop tt->restore after successful restore - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/941ac10529b3be5965a88d432a161ab459672ba8

Vendor Advisories for CVE-2026-89815(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 27× in last 7d / 82× 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-10-05 03:22 UTCEG score recompute
  2. 2026-10-05 03:22 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 15:21 UTCGHSA enrichment
  5. 2026-10-04 03:16 UTCGHSA enrichment
  6. 2026-10-03 15:15 UTCEG score recompute
  7. 2026-10-03 15:15 UTCGHSA enrichment
  8. 2026-10-03 03:14 UTCEG score recompute
  9. 2026-10-03 03:14 UTCGHSA enrichment
  10. 2026-10-02 15:13 UTCGHSA enrichment
  11. 2026-10-02 03:12 UTCEG score recompute
  12. 2026-10-02 03:12 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 14:53 UTCGHSA enrichment
  15. 2026-10-01 02:52 UTCEG score recompute
  16. 2026-10-01 02:52 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 14:52 UTCGHSA enrichment
  19. 2026-09-30 02:50 UTCEG score recompute
  20. 2026-09-30 02:50 UTCGHSA enrichment
  21. 2026-09-29 14:49 UTCGHSA enrichment
  22. 2026-09-29 02:43 UTCEG score recompute
  23. 2026-09-29 02:43 UTCGHSA enrichment
  24. 2026-09-28 14:42 UTCEG score recompute
  25. 2026-09-28 14:42 UTCGHSA enrichment
Show 57 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 13:52 UTCEPSS rescore
  3. 2026-09-28 02:41 UTCGHSA enrichment
  4. 2026-09-27 14:40 UTCEG score recompute
  5. 2026-09-27 14:40 UTCGHSA enrichment
  6. 2026-09-27 13:49 UTCEPSS rescore
  7. 2026-09-27 02:40 UTCEG score recompute
  8. 2026-09-27 02:40 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 14:38 UTCGHSA enrichment
  11. 2026-09-26 02:28 UTCEG score recompute
  12. 2026-09-26 02:28 UTCGHSA enrichment
  13. 2026-09-25 14:28 UTCGHSA enrichment
  14. 2026-09-25 02:27 UTCGHSA enrichment
  15. 2026-09-24 14:26 UTCEG score recompute
  16. 2026-09-24 14:26 UTCGHSA enrichment
  17. 2026-09-24 14:04 UTCEPSS rescore
  18. 2026-09-24 02:25 UTCEG score recompute
  19. 2026-09-24 02:24 UTCGHSA enrichment
  20. 2026-09-23 17:54 UTCEPSS rescore
  21. 2026-09-23 14:24 UTCGHSA enrichment
  22. 2026-09-23 02:23 UTCEG score recompute
  23. 2026-09-23 02:23 UTCGHSA enrichment
  24. 2026-09-22 16:01 UTCEPSS rescore
  25. 2026-09-22 14:22 UTCGHSA enrichment
  26. 2026-09-22 02:22 UTCEG score recompute
  27. 2026-09-22 02:21 UTCGHSA enrichment
  28. 2026-09-21 21:09 UTCEPSS rescore
  29. 2026-09-21 14:20 UTCEG score recompute
  30. 2026-09-21 14:20 UTCGHSA enrichment
  31. 2026-09-21 13:20 UTCEG score recompute
  32. 2026-09-21 13:20 UTCGHSA enrichment
  33. 2026-09-21 03:40 UTCEG score recompute
  34. 2026-09-21 03:40 UTCGHSA enrichment
  35. 2026-09-20 20:16 UTCEPSS rescore
  36. 2026-09-20 15:40 UTCGHSA enrichment
  37. 2026-09-20 03:38 UTCEG score recompute
  38. 2026-09-20 03:38 UTCGHSA enrichment
  39. 2026-09-19 15:37 UTCGHSA enrichment
  40. 2026-09-19 03:34 UTCEG score recompute
  41. 2026-09-19 03:34 UTCGHSA enrichment
  42. 2026-09-18 19:28 UTCEPSS rescore
  43. 2026-09-18 15:33 UTCGHSA enrichment
  44. 2026-09-18 03:31 UTCEG score recompute
  45. 2026-09-18 03:31 UTCGHSA enrichment
  46. 2026-09-17 19:32 UTCEPSS rescore
  47. 2026-09-17 15:30 UTCGHSA enrichment
  48. 2026-09-17 03:25 UTCEG score recompute
  49. 2026-09-17 03:25 UTCGHSA enrichment
  50. 2026-09-16 15:24 UTCEG score recompute
  51. 2026-09-16 15:24 UTCGHSA enrichment
  52. 2026-09-16 14:49 UTCEG score recompute▲ 7.80
  53. 2026-09-16 14:49 UTCGHSA enrichment
  54. 2026-09-16 14:45 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  55. 2026-09-16 11:21 UTCNVD update
  56. 2026-09-16 10:41 UTCEG score recompute
  57. 2026-09-16 10:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-89815?
CVE-2026-89815 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Drop tt->restore after successful restore ttmpoolrestoreandalloc() can successfully complete the restore process via ttmpoolrestore_commit(), but tt->restore is not dropped afterward. As a result, subsequent backup/restore…
When was CVE-2026-89815 disclosed?
CVE-2026-89815 was first published on September 16, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89815 actively exploited?
CVE-2026-89815 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-89815?
CVE-2026-89815 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89815?
No fix for CVE-2026-89815 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-89815 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-89815

Explore →

Is Your Infrastructure Affected by CVE-2026-89815?

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

Book a Demo →Browse All CVEs