Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43128RDMA/umem: Fix double dma_buf_unpin in failure path

Description

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

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43128, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 1e4df4a21c5ac722df1099eee30cad9246c889b5 – < 70542b69abff34d24b11ae0bb200cc7a766d18df
    • affected 1e4df4a21c5ac722df1099eee30cad9246c889b5 – < b324327ff6f48d8065dca67eb3b91357e72726bd
    • affected 1e4df4a21c5ac722df1099eee30cad9246c889b5 – < ba3bf0f1bf1d5d0404678485e872980532fcc2c4
    • affected 1e4df4a21c5ac722df1099eee30cad9246c889b5 – < d3e32e2f3262f1b25d77c085ace38e2cc4ad75cf
    • affected 1e4df4a21c5ac722df1099eee30cad9246c889b5 – < 40126bcbefa79ea86672e05dae608596bab38319
    • affected 1e4df4a21c5ac722df1099eee30cad9246c889b5 – < 104016eb671e19709721c1b0048dd912dc2e96be
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43128 badge
[![CVE-2026-43128](https://cveledger.app/badge/CVE-2026-43128.svg)](https://cveledger.app/cve/CVE-2026-43128)

Record last updated .