CVE-2026-43399

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-08. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 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/userq: Fix reference leak in amdgpu_userq_wait_ioctl

Drop reference to syncobj and timeline fence when aborting the ioctl due output array being too small.

(cherry picked from commit 68951e9c3e6bb22396bc42ef2359751c8315dd27)

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 21, 2026

Advisory Details (3)

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

drm/amdgpu/userq: Fix reference leak in amdgpu_userq_wait_ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/762f47e2b824383d5be65eee2c40a1269b7d50c8
generic

drm/amdgpu/userq: Fix reference leak in amdgpu_userq_wait_ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5409247d41f372bec5b141ef599f2d9f5e81b746
generic

drm/amdgpu/userq: Fix reference leak in amdgpu_userq_wait_ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49abfa812617a7f2d0132c70d23ac98b389c6ec1

Vendor Advisories for CVE-2026-43399(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.19osv

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 (119 versions)6.19.10-1

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43399?
CVE-2026-43399 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: Fix reference leak in amdgpuuserqwait_ioctl Drop reference to syncobj and timeline fence when aborting the ioctl due output array being too small. (cherry picked from commit…
When was CVE-2026-43399 disclosed?
CVE-2026-43399 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43399 actively exploited?
CVE-2026-43399 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-43399?
CVE-2026-43399 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43399?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43399, 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-43399

Explore →

Is Your Infrastructure Affected by CVE-2026-43399?

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