CVE-2026-43128

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.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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

RDMA/umem: Fix double dma_buf_unpin in failure path

In ib_umem_dmabuf_get_pinned_with_dma_device(), the call to ib_umem_dmabuf_map_pages() can fail. If this occurs, the dmabuf is immediately unpinned but the umem_dmabuf->pinned flag is still set. Then, when ib_umem_release() is called, it calls ib_umem_dmabuf_revoke() which will call dma_buf_unpin() again.

Fix this by removing the immediate unpin upon failure and just let the ib_umem_release/revoke path handle it. This also ensures the proper unmap-unpin unwind ordering if the dmabuf_map_pages call happened to fail due to dma_resv_wait_timeout (and therefore has a non-NULL umem_dmabuf->sgt).

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

Published

May 6, 2026

Last Modified

May 8, 2026

Advisory Details (6)

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

RDMA/umem: Fix double dma_buf_unpin in failure path - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/umem: Fix double dma_buf_unpin in failure path - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/umem: Fix double dma_buf_unpin in failure path - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/umem: Fix double dma_buf_unpin in failure path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70542b69abff34d24b11ae0bb200cc7a766d18df
generic

RDMA/umem: Fix double dma_buf_unpin in failure path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40126bcbefa79ea86672e05dae608596bab38319
generic

RDMA/umem: Fix double dma_buf_unpin in failure path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/104016eb671e19709721c1b0048dd912dc2e96be

Vendor Advisories for CVE-2026-43128(7)

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.16.1.el10_22026-05-20redhat
redhatkernel-0:5.14.0-687.10.1.el9_82026-05-20redhat
linuxKernel @ 6.1.165—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.

Weakness Classification(1)

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

Data Freshness Timeline

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

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

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

Frequently asked(5)

What is CVE-2026-43128?
CVE-2026-43128 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/umem: Fix double dmabufunpin in failure path In ibumemdmabufgetpinnedwithdma_device(), the call to ibumemdmabufmappages() can fail. If this occurs, the dmabuf is immediately unpinned but the umem_dmabuf->pinned flag is still…
When was CVE-2026-43128 disclosed?
CVE-2026-43128 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43128 actively exploited?
CVE-2026-43128 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43128?
CVE-2026-43128 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43128?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43128, 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-43128

Explore →

Is Your Infrastructure Affected by CVE-2026-43128?

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

Start Free Scan →Browse All CVEs