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.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/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)
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
3%
KEV
Not listed

Published

April 24, 2026

Last Modified

August 5, 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(2)

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

Patch Availability(14)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1

Weakness Classification(1)

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

Additional Vendor Advisories

(13)

Data Freshness Timeline

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

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

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

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