RDMA/cxgb4: Cancel reg_work before freeing device on remove
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1c8f1da5d851b92aeb81dbbb9ebd516f6e2588f5 · < 85f438382a865a4dc4c50e6b884310bb2b60fc4d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
RDMA/cxgb4: Cancel reg_work before freeing device on remove
c4iw_uld_state_change() queues reg_work to register the RDMA device. c4iw_remove() can free ctx->dev while this work is pending or running, leaving c4iw_register_device() accessing the freed device.
Cancel reg_work before removing the device. The registration work can tear down ctx->dev when registration fails, so do not unregister or deallocate it again in that case.
This issue was found by an in-house static analysis tool.
From the CVE record · Linux
In the Linux kernel’s RDMA/cxgb4 component, device removal can free an RDMA device while registration work is pending or running, allowing that work to access freed memory. The input does not specify how an attacker could trigger the condition or whether network access, authentication, or user interaction is required.
Teams running Linux kernels with the RDMA/cxgb4 component should check their deployments; affected versions are not specified.