CVE-2026-31566

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib

amdgpu_amdkfd_submit_ib() submits a GPU job and gets a fence from amdgpu_ib_schedule(). This fence is used to wait for job completion.

Currently, the code drops the fence reference using dma_fence_put() before calling dma_fence_wait().

If dma_fence_put() releases the last reference, the fence may be freed before dma_fence_wait() is called. This can lead to a use-after-free.

Fix this by waiting on the fence first and releasing the reference only after dma_fence_wait() completes.

Fixes the below: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:697 amdgpu_amdkfd_submit_ib() warn: passing freed memory 'f' (line 696)

(cherry picked from commit 8b9e5259adc385b61a6590a13b82ae0ac2bd3482)

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
2.6%
KEV
Not listed

Published

April 24, 2026

Last Modified

April 27, 2026

Advisory Details (6)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7150850146ebfa4ca998f653f264b8df6f7f85be
generic

drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42d248726a0837640452b71c5a202ca3d35239ec
generic

drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39820864eacd886f1a6f817414fb8f9ea3e9a2b4
generic

drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/138e42be35ff2ce6572ae744de851ea286cf3c69

Vendor Advisories for CVE-2026-31566(1)

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 8× in last 7d / 40× 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 159 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31566?
CVE-2026-31566 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix fence put before wait in amdgpuamdkfdsubmit_ib amdgpuamdkfdsubmit_ib() submits a GPU job and gets a fence from amdgpuibschedule(). This fence is used to wait for job completion. Currently, the code drops the fence…
When was CVE-2026-31566 disclosed?
CVE-2026-31566 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on April 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31566 actively exploited?
CVE-2026-31566 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31566?
CVE-2026-31566 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31566?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31566, 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-31566

Explore →

Is Your Infrastructure Affected by CVE-2026-31566?

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

Start Free Scan →Browse All CVEs