PT-2026-151733

CVE-2026-99522

·

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/irdma: avoid use-after-free in icrdma remove
icrdma remove() dereferences iwdev after calling irdma ib unregister device():
irdma ib unregister device(iwdev) -> ib unregister device(&iwdev->ibdev) -> ib unregister device() -> ib dealloc device()
irdma registers irdma ib dealloc device() as the dealloc driver callback in its ib device ops. The RDMA core explicitly documents ib unregister device() that when ops.dealloc driver is used, ib dev will be freed upon return from the function.
The ib device is embedded in struct irdma device and iwdev itself was allocated by ib alloc device(irdma device, ibdev). Consequently, once irdma ib unregister device() returns, iwdev must no longer be dereferenced.
However, icrdma remove() currently accesses iwdev->rf afterwards when deinitializing interrupts, destroying ah tbl lock, and freeing rf. Although the final ib device storage is released with kfree rcu(), the object lifetime has already ended and callers must not rely on the RCU grace period to continue dereferencing iwdev.
Save iwdev->rf before unregistering the RDMA device and use the saved pointer for the remaining cleanup.
This issue was found by manual code inspection.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾