GPU VulnDB

Database/Firmware, BMC & network fabric

Linux kernel RDMA/cxgb4: use-after-free if device removal races the deferred RDMA registration work

UnscoredCVE-2026-89510Firmware, BMC & network fabriccurated

Impact

c4iw_uld_state_change() queues reg_work to register the iWARP device, and c4iw_remove() can free ctx->dev while that work is still pending or running, leaving c4iw_register_device() touching freed memory. The practical exposure is small and worth stating plainly: it only fires on Chelsio T4/T5 adapters, only during driver teardown or PCI hotplug, and only root can drive that - there is no tenant-reachable path here. The consequence if it does fire is host memory corruption during a maintenance action on a node, which is the worst time to discover it. Found by an in-house static analysis tool, with no evidence of exploitation in the record.

Who can reach it

Local root, or an automated process that unloads or hot-removes the cxgb4 device, on a host with Chelsio iWARP hardware. Not reachable by unprivileged users or tenants.

What to do

Pick up the stable kernel update that cancels reg_work before device removal (four stable commits linked) and reboot the node; the change can be deferred to the next routine kernel maintenance window given the root-only trigger. Until then, avoid unloading or hot-removing cxgb4 on production nodes. The record names no fixed release numbers.

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.