GPU VulnDB

Database/Firmware, BMC & network fabric

Linux kernel RDMA/ucma: use-after-free on the event list when SET_OPTION races context migration

UnscoredCVE-2026-89508Firmware, BMC & network fabriccurated

Impact

ucma_set_ib_path() invokes ucma_event_handler() directly from the write() path without the handler lock that keeps ctx->file stable. A concurrent ucma_migrate_id() reassigns ctx->file while the SET_OPTION caller sleeps in mutex_lock(), so the event is added to file B's event_list while only file A's mutex is held. The reported outcome is a KASAN slab-use-after-free on an event another thread already dequeued and freed, plus file A's mutex left held, wedging its next writer in uninterruptible sleep. Unlike CVE-2026-89507 this path needs a bound, address-resolved cm_id, so an RDMA device must be present - on an InfiniBand or RoCE GPU fabric node that is the normal case. A use-after-free in a path any local user can drive is a node-integrity problem, not just a crash.

Who can reach it

Local unprivileged user on a node that has an RDMA device, via the world-writable /dev/infiniband/rdma_cm. No capabilities required; the caller must be able to bind and resolve a cm_id, which an ordinary user can do.

What to do

Apply the stable kernel update that takes the handler lock around the call (four stable commits linked) and reboot each node. No fixed version numbers are given in the record. Restricting /dev/infiniband/rdma_cm access for workloads that do not need rdma_cm removes the exposure without a reboot.

References

Related entries

All Firmware, BMC & network fabric entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.