CVE-2026-43237

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. 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: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4

This commit simplifies the amdgpu_gem_va_ioctl function, key updates include:

  • Moved the logic for managing the last update fence directly into
amdgpu_gem_va_update_vm.
  • Introduced checks for the timeline point to enable conditional
replacement or addition of fences.

v2: Addressed review comments from Christian. v3: Updated comments (Christian). v4: The previous version selected the fence too early and did not manage its reference correctly, which could lead to stale or freed fences being used. This resulted in refcount underflows and could crash when updating GPU timelines. The fence is now chosen only after the VA mapping work is completed, and its reference is taken safely. After exporting it to the VM timeline syncobj, the driver always drops its local fence reference, ensuring balanced refcounting and avoiding use-after-free on dma_fence.

Crash signature: [ 205.828135] refcount_t: underflow; use-after-free. [ 205.832963] WARNING: CPU: 30 PID: 7274 at lib/refcount.c:28 refcount_warn_saturate+0xbe/0x110 ... [ 206.074014] Call Trace: [ 206.076488] [ 206.078608] amdgpu_gem_va_ioctl+0x6ea/0x740 [amdgpu] [ 206.084040] ? __pfx_amdgpu_gem_va_ioctl+0x10/0x10 [amdgpu] [ 206.089994] drm_ioctl_kernel+0x86/0xe0 [drm] [ 206.094415] drm_ioctl+0x26e/0x520 [drm] [ 206.098424] ? __pfx_amdgpu_gem_va_ioctl+0x10/0x10 [amdgpu] [ 206.104402] amdgpu_drm_ioctl+0x4b/0x80 [amdgpu] [ 206.109387] __x64_sys_ioctl+0x96/0xe0 [ 206.113156] do_syscall_64+0x66/0x2d0 ... [ 206.553351] BUG: unable to handle page fault for address: ffffffffc0dfde90 ... [ 206.553378] RIP: 0010:dma_fence_signal_timestamp_locked+0x39/0xe0 ... [ 206.553405] Call Trace: [ 206.553409] [ 206.553415] ? __pfx_drm_sched_fence_free_rcu+0x10/0x10 [gpu_sched] [ 206.553424] dma_fence_signal+0x30/0x60 [ 206.553427] drm_sched_job_done.isra.0+0x123/0x150 [gpu_sched] [ 206.553434] dma_fence_signal_timestamp_locked+0x6e/0xe0 [ 206.553437] dma_fence_signal+0x30/0x60 [ 206.553441] amdgpu_fence_process+0xd8/0x150 [amdgpu] [ 206.553854] sdma_v4_0_process_trap_irq+0x97/0xb0 [amdgpu] [ 206.554353] edac_mce_amd(E) ee1004(E) [ 206.554270] amdgpu_irq_dispatch+0x150/0x230 [amdgpu] [ 206.554702] amdgpu_ih_process+0x6a/0x180 [amdgpu] [ 206.555101] amdgpu_irq_handler+0x23/0x60 [amdgpu] [ 206.555500] __handle_irq_event_percpu+0x4a/0x1c0 [ 206.555506] handle_irq_event+0x38/0x80 [ 206.555509] handle_edge_irq+0x92/0x1e0 [ 206.555513] __common_interrupt+0x3e/0xb0 [ 206.555519] common_interrupt+0x80/0xa0 [ 206.555525] [ 206.555527] ... [ 206.555650] RIP: 0010:dma_fence_signal_timestamp_locked+0x39/0xe0 ... [ 206.555667] Kernel panic - not syncing: Fatal exception in interrupt

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
2%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated May 20, 2026
No patch confirmed yet.
generic

drm/amdgpu: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4 - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4 - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0399b8416ecf64ef86ad23401fe23eabdb07831a

Vendor Advisories for CVE-2026-43237(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-211.49.1.el10_22026-08-20redhat
redhatkernel-0:5.14.0-687.41.1.el9_82026-08-20redhat
linuxKernel @ 6.18.16—osv

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (113 versions)6.19.6-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 4× in last 7d / 69× 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 234 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43237?
CVE-2026-43237 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Refactor amdgpugemva_ioctl for Handling Last Fence Update and Timeline Management v4 This commit simplifies the amdgpugemva_ioctl function, key updates include: Moved the logic for managing the last update fence…
When was CVE-2026-43237 disclosed?
CVE-2026-43237 was first published in the National Vulnerability Database on May 6, 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-43237 actively exploited?
CVE-2026-43237 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-43237?
CVE-2026-43237 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43237?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43237, 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-43237

Explore →

Is Your Infrastructure Affected by CVE-2026-43237?

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

Start Free Scan →Browse All CVEs