CVE-2026-53143

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: 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.0
EG Score
7.0(high)
EPSS
3.3%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 30, 2026

Advisory Details (8)

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

Affected: Red Hat Enterprise Linux 10",

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53143.json
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(1)

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

Data Freshness Timeline

(refreshed 41× in last 7d / 54× 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-07-06 20:27 UTCEG score recompute
  2. 2026-07-06 20:27 UTCVendor advisory
  3. 2026-07-06 20:26 UTCGHSA enrichment
  4. 2026-07-06 08:03 UTCEG score recompute
  5. 2026-07-06 08:03 UTCVendor advisory
  6. 2026-07-06 08:02 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 19:40 UTCEG score recompute
  10. 2026-07-05 19:40 UTCVendor advisory
  11. 2026-07-05 19:40 UTCGHSA enrichment
  12. 2026-07-05 07:30 UTCEG score recompute
  13. 2026-07-05 07:30 UTCVendor advisory
  14. 2026-07-05 07:30 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 19:19 UTCEG score recompute
  18. 2026-07-04 19:19 UTCVendor advisory
  19. 2026-07-04 19:18 UTCGHSA enrichment
  20. 2026-07-04 07:08 UTCEG score recompute
  21. 2026-07-04 07:08 UTCVendor advisory
  22. 2026-07-04 07:08 UTCGHSA enrichment
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-03 18:48 UTCEG score recompute
Show 29 more
  1. 2026-07-03 18:48 UTCVendor advisory
  2. 2026-07-03 18:48 UTCGHSA enrichment
  3. 2026-07-03 06:38 UTCEG score recompute
  4. 2026-07-03 06:38 UTCVendor advisory
  5. 2026-07-03 06:38 UTCGHSA enrichment
  6. 2026-07-02 18:21 UTCEG score recompute
  7. 2026-07-02 18:21 UTCVendor advisory
  8. 2026-07-02 18:21 UTCGHSA enrichment
  9. 2026-07-02 06:11 UTCEG score recompute
  10. 2026-07-02 06:11 UTCVendor advisory
  11. 2026-07-02 06:11 UTCGHSA enrichment
  12. 2026-07-01 18:00 UTCEG score recompute▲ 7.00
  13. 2026-07-01 18:00 UTCVendor advisory
  14. 2026-07-01 18:00 UTCGHSA enrichment
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 04:34 UTCNVD updateCVSS v3 → 7 · severity → HIGH
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 14:05 UTCEG score recompute
  22. 2026-06-28 14:05 UTCVendor advisory
  23. 2026-06-28 14:05 UTCGHSA enrichment
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 04:56 UTCEPSS rescore
  26. 2026-06-27 03:08 UTCEPSS rescore
  27. 2026-06-25 13:49 UTCEPSS rescore
  28. 2026-06-25 10:09 UTCEG score recompute
  29. 2026-06-25 10:09 UTCGHSA enrichment

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 June 30, 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 3.3% 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.0 (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.

Start Free Scan →Browse All CVEs