PT-2026-151734

CVE-2026-99523

·

Published

2026-11-19

·

Updated

2026-11-19

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

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 hw destroy rwsem for write, uverbs uobject release() fails its trylock and leaves the uobject on the ufile list, but the dma buf is freed as soon as the release returns. The cleanup then destroys the uobject and uses the freed dma buf:
BUG: KASAN: slab-use-after-free in uverbs dmabuf fd destroy uobj+0x46/0x200 Read of size 8 at addr ff11000109cf14b0 by task repro/435 Call Trace: uverbs dmabuf fd destroy uobj+0x46/0x200 destroy hw fd uobject+0x3f/0x50 uverbs destroy uobject+0xc5/0x380 uverbs cleanup ufile+0x1a8/0x260 uverbs destroy ufile hw+0x54/0x160 ib uverbs close+0x34/0x110 Allocated by task 435: dma buf export+0x1b5/0x530 ib uverbs handler UVERBS METHOD DMABUF ALLOC+0x223/0x3f0 Freed by task 436: kfree+0x301/0x530 dentry kill+0x14c/0x560 fput+0x23a/0x4a0
rdma user mmap entry remove() dereferences the same pointer.
Protect the stored dma buf 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 uverbs uobject release() 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.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾