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.2%, top 95% 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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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 PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 20, 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(4)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-18ubuntu
redhatkernel-0:6.12.0-211.49.1.el10_22026-08-20redhat
redhatkernel-0:5.14.0-687.41.1.el9_82026-08-20redhat

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 rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

Weakness Classification(2)

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

Additional Vendor Advisories

(4)

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 15× in last 7d / 63× 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 307 total refreshes for this CVE.

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

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 August 20, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 95.2% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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