CVE-2026-43128
What it is
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).
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-415
- Record status
- Modified
Affected
- Linux Kernel < 6.1.165
- Linux Kernel < 6.6.128
- Linux Kernel < 6.12.75
- Linux Kernel < 6.18.16
- Linux Kernel < 6.19.6
- Linux Kernel 7.0
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-43128.md and follow it. Check whether this project is affected by CVE-2026-43128. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- 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
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