RDMA/umem: Fix double dma_buf_unpin in failure path
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).
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.165, 6.12.75, 6.18.16, 6.19.6, 6.6.128
- CVEs
- CVE-2026-43128
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 17:32 UTC · Revision 1
Source evidence
RDMA/umem: Fix double dma_buf_unpin in failure path
core-osv · Original sourcePublished 6 May 2026, 11:27 UTC
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).
osv:CVE-2026-43128
Kernel
Fixed versions: 6.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6
Complete source record
{
"id": "375020bf86ccf7bdfea264c496502b7bca0e95fd21b8515eaa89edb81104ec98",
"url": "https://osv.dev/vulnerability/CVE-2026-43128",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "RDMA/umem: Fix double dma_buf_unpin in failure path",
"summary": "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).",
"evidence": "osv:CVE-2026-43128",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.165",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.128",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.75",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.16",
"evidence": "/affected/1/ranges"
},
{
"value": "6.19.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-43128",
"aliases": [
"CVE-2026-43128"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "1e4df4a21c5ac722df1099eee30cad9246c889b5"
},
{
"fixed": "70542b69abff34d24b11ae0bb200cc7a766d18df"
},
{
"fixed": "b324327ff6f48d8065dca67eb3b91357e72726bd"
},
{
"fixed": "ba3bf0f1bf1d5d0404678485e872980532fcc2c4"
},
{
"fixed": "d3e32e2f3262f1b25d77c085ace38e2cc4ad75cf"
},
{
"fixed": "40126bcbefa79ea86672e05dae608596bab38319"
},
{
"fixed": "104016eb671e19709721c1b0048dd912dc2e96be"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43128.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.165"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.128"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.75"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.16"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "6.19.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43128.json"
}
}
],
"modified": "2026-10-28T02:30:30.831378652Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/104016eb671e19709721c1b0048dd912dc2e96be",
"https://git.kernel.org/stable/c/40126bcbefa79ea86672e05dae608596bab38319",
"https://git.kernel.org/stable/c/70542b69abff34d24b11ae0bb200cc7a766d18df",
"https://git.kernel.org/stable/c/b324327ff6f48d8065dca67eb3b91357e72726bd",
"https://git.kernel.org/stable/c/ba3bf0f1bf1d5d0404678485e872980532fcc2c4",
"https://git.kernel.org/stable/c/d3e32e2f3262f1b25d77c085ace38e2cc4ad75cf",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43128.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-43128",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43128.json"
}
},
"related_cves": [
{
"value": "CVE-2026-43128",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 497855,
"published_at": "2026-05-06T11:27:17.474+00:00"
}