GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel RDMA/erdma: completion queue freed while an in-flight EQ handler still references it

CVSS 7.8CVE-2026-90309Kernel, userspace & hypervisorcurated

Impact

EQ handlers resolve CQs from dev->cq_xa and then call completion or error callbacks after releasing the xarray lock. erdma_destroy_cq() can erase the CQ and free its queue buffer and doorbell record while a previously scheduled EQ handler is still running against it, a use-after-free on freed DMA-visible structures (NVD: 7.8, local, full impact). The fix adds a CQ refcount acquired with refcount_inc_not_zero() under the xarray lock and waits for in-flight EQ users before releasing resources. This is a distinct code path and a distinct fix from the QP refcount issue tracked as CVE-2026-90308, so both patches are needed; it applies only to nodes running Alibaba Cloud Elastic RDMA.

Who can reach it

Local, authenticated: a process or container with an erdma uverbs device that can destroy a CQ while completion or error events for it are still being dispatched. No remote vector; absent on nodes without the erdma driver.

What to do

Update to a stable kernel containing the listed commits and reboot; drain the node first because the affected code is in the RDMA completion path. Nodes without the erdma module need no action. The record names no fixed release, only the stable commits.

References

Related entries

All Kernel, userspace & hypervisor 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.