CVE-2026-53143

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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

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

drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11

The v11 MQD manager incorrectly assigned the CP-compute variants of checkpoint_mqd/restore_mqd for KFD_MQD_TYPE_SDMA queues. These functions use sizeof(struct v11_compute_mqd) (2048 bytes) instead of sizeof(struct v11_sdma_mqd) (512 bytes), causing a 1536-byte overflow.

During CRIU checkpoint of an SDMA queue on Navi3x:

  • checkpoint_mqd() reads 2048 bytes from a 512-byte SDMA MQD buffer,
leaking 1536 bytes of adjacent GTT memory to userspace

During CRIU restore:

  • restore_mqd() writes 2048 bytes into a 512-byte SDMA MQD buffer,
corrupting 1536 bytes of adjacent GTT memory (often the ring buffer or neighboring MQDs)

This is a copy-paste regression unique to v11. All other ASIC backends (cik, vi, v9, v10, v12) correctly use the SDMA-specific variants.

Add checkpoint_mqd_sdma() and restore_mqd_sdma() functions that properly handle the smaller v11_sdma_mqd structure, matching the pattern used in other MQD managers.

(cherry picked from commit 6fa41db7ffdec97d62433adf03b7b9b759af8c2c)

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS
4.0%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 15, 2026

Advisory Details (8)

Auto-updated Jun 30, 2026
Patch available. Sources: redhat.
redhat

2492719 – (CVE-2026-53143) CVE-2026-53143 kernel: drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11

https://bugzilla.redhat.com/show_bug.cgi?id=2492719
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-53143
generic

drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/352ea59028ea48a6fff77f19ae28f98f71946a80
generic

drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c5b66c9b4057b385566940935ebc32f6e6ebfd2
generic

drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/16dad1fb0d783a4008de30e32d0038c393de05b1

Vendor Advisories for CVE-2026-53143(2)

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

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 108× 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 108 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53143?
CVE-2026-53143 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 The v11 MQD manager incorrectly assigned the CP-compute variants of checkpointmqd/restoremqd for KFDMQDTYPE_SDMA queues. These functions use sizeof(struct…
When was CVE-2026-53143 disclosed?
CVE-2026-53143 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53143 actively exploited?
CVE-2026-53143 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53143?
CVE-2026-53143 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53143?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53143, 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

Explore the affected products and dependency analysis for CVE-2026-53143

Explore →

Is Your Infrastructure Affected by CVE-2026-53143?

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