CVE-2026-89811

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.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: 8.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/amdkfd: Add TLB flush after MES queue eviction/suspension

MES (Micro Engine Scheduler) does not perform heavy-weight TLB invalidation after unmapping queues, unlike HWS which does this automatically. This causes a race condition where in-flight DMA descriptors can access memory that has been unmapped, leading to page faults and GPU queue hangs during SVM page migration.

The issue manifests as KFDSVMRangeTest.MultiThreadMigrationTest failures on gfx1151 (Strix Point) with XNACK mode 1 enabled - the GPU compute queue hangs with packets submitted but never consumed.

Add kfd_flush_tlb() calls after MES queue removal in two locations:

  • evict_process_queues_cpsch(): after all queues removed during eviction
  • suspend_queues(): after debug/criu queue suspension (with mem_fence barrier)

This ensures all in-flight memory accesses from unmapped queues are flushed before memory is freed or migrated.

(cherry picked from commit f5c4f88e0f9c45a8fb9dfac0c1df726c95e41b77)

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
44
EG Risk 44/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
Severity88% × 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 17, 2026

Advisory Details (3)

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

drm/amdkfd: Add TLB flush after MES queue eviction/suspension - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94e25cb6ab7f4f025bcdcd8ea79fda30f12843a4
generic

drm/amdkfd: Add TLB flush after MES queue eviction/suspension - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6aae545c87087e4dc96e205452243813bfa73ba2
generic

drm/amdkfd: Add TLB flush after MES queue eviction/suspension - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e230c546ed93741833ab5babb0b202f9c2052b45

Vendor Advisories for CVE-2026-89811(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
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 39× in last 7d / 113× 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.

Showing the most recent 100 of 113 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-89811?
CVE-2026-89811 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Add TLB flush after MES queue eviction/suspension MES (Micro Engine Scheduler) does not perform heavy-weight TLB invalidation after unmapping queues, unlike HWS which does this automatically. This causes a race…
When was CVE-2026-89811 disclosed?
CVE-2026-89811 was first published on September 16, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89811 actively exploited?
CVE-2026-89811 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-89811?
CVE-2026-89811 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89811?
No fix for CVE-2026-89811 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-89811 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-89811

Explore →

Is Your Infrastructure Affected by CVE-2026-89811?

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

Book a Demo →Browse All CVEs