CVE-2026-43400

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.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: 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: add upper bound check on user inputs in signal ioctl

Huge input values in amdgpu_userq_signal_ioctl can lead to a OOM and could be exploited.

So check these input value against AMDGPU_USERQ_MAX_HANDLES which is big enough value for genuine use cases and could potentially avoid OOM.

(cherry picked from commit be267e15f99bc97cbe202cd556717797cdcf79a5)

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
2.7%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 21, 2026

Advisory Details (3)

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

drm/amdgpu: add upper bound check on user inputs in signal ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: add upper bound check on user inputs in signal ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6fff5204d8aa26b1be50b6427f833bd3e8899c4f
generic

drm/amdgpu: add upper bound check on user inputs in signal ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46630d966b99b0fc6cb01fef4110587f3375a0c0

Vendor Advisories for CVE-2026-43400(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43400?
CVE-2026-43400 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: add upper bound check on user inputs in signal ioctl Huge input values in amdgpuuserqsignal_ioctl can lead to a OOM and could be exploited. So check these input value against AMDGPUUSERQMAX_HANDLES which is big enough…
When was CVE-2026-43400 disclosed?
CVE-2026-43400 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-43400 actively exploited?
CVE-2026-43400 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43400?
CVE-2026-43400 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43400?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43400, 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-43400

Explore →

Is Your Infrastructure Affected by CVE-2026-43400?

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

Start Free Scan →Browse All CVEs