CVE-2026-99523: RDMA/uverbs: Fix DMABUF use-after-free during ufile cleanup
In the Linux kernel, the following vulnerability has been resolved:
RDMA/uverbs: Fix DMABUF use-after-free during ufile cleanup
The DMABUF release can race with ufile cleanup. When the cleanup holds hwdestroyrwsem for write, uverbsuobjectrelease() fails its trylock and leaves the uobject on the ufile list, but the dmabuf is freed as soon as the release returns. The cleanup then destroys the uobject and uses the freed dmabuf:
BUG: KASAN: slab-use-after-free in uverbsdmabuffddestroyuobj+0x46/0x200 Read of size 8 at addr ff11000109cf14b0 by task repro/435 Call Trace: uverbsdmabuffddestroyuobj+0x46/0x200 destroyhwfduobject+0x3f/0x50 uverbsdestroyuobject+0xc5/0x380 uverbscleanupufile+0x1a8/0x260 uverbsdestroyufilehw+0x54/0x160 ibuverbsclose+0x34/0x110 Allocated by task 435: dmabufexport+0x1b5/0x530 ibuverbshandlerUVERBSMETHODDMABUFALLOC+0x223/0x3f0 Freed by task 436: kfree+0x301/0x530 dentrykill+0x14c/0x560 fput+0x23a/0x4a0
rdmausermmapentryremove() dereferences the same pointer.
Protect the stored dmabuf pointer with a mutex and clear it before release returns. Use a shared revoke helper so uobject destruction and mmap entry removal both skip a cleared pointer. Hold a temporary uobject reference across uverbsuobjectrelease() and the pointer update.
Use a separate mutex because uobject destruction can free the mmap entry before release finishes. Map and unmap use attachment->dmabuf directly, so they do not need to take the new mutex while holding the reservation lock.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.3-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1