GPU VulnDB

Database/Firmware, BMC & network fabric

Linux kernel RDMA/ucma: unprivileged event-list corruption when a context is migrated mid-write

UnscoredCVE-2026-89507Firmware, BMC & network fabriccurated

Impact

ucma_write_cm_event() queues a uevent without holding the handler lock and re-reads ctx->file for each dereference, so a concurrent ucma_migrate_id() can swap the file between the mutex_lock() and the list_add_tail(). The result in the report is list corruption and a kernel BUG, file A's mutex left held forever (its next writer is stuck in D state), and a uevent stranded on a list the cleanup path never walks, so it outlives its context. What makes this one worth attention is reach: /dev/infiniband/rdma_cm is mode 0666 and no RDMA device has to be present, so any local unprivileged user - including a tenant in a container where /dev/infiniband is exposed - can trigger it. On a GPU node the cost is a panic or a permanently wedged writer, and clearing it means a reboot of a node that is expensive to drain.

Who can reach it

Any local unprivileged user who can open /dev/infiniband/rdma_cm, which is world-writable by default. No RDMA hardware, no capabilities and no authentication beyond a shell on the node (or a pod with that device node exposed).

What to do

Take the stable kernel update carrying the fix (the three stable commits are linked) and reboot each node; there is no live mitigation in the record short of blocking access to /dev/infiniband/rdma_cm for untrusted users, which is a reasonable interim step on nodes where tenants do not use rdma_cm. The record names no fixed release numbers, only the commits.

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.