RDMA/irdma: Fix deadlock during netdev reset with active connections
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c8f304d75f6c6cc679a73f89591f9a915da38f09 · < 464bbb844ba5b68e038220c34019069a0a9f1581| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
RDMA/irdma: Fix deadlock during netdev reset with active connections
Resolve deadlock that occurs when user executes netdev reset while RDMA applications (e.g., rping) are active. The netdev reset causes ice driver to remove irdma auxiliary driver, triggering device_delete and subsequent client removal. During client removal, uverbs_client waits for QP reference count to reach zero while cma_client holds the final reference, creating circular dependency and indefinite wait in iWARP mode. Skip QP reference count wait during device reset to prevent deadlock.
From the CVE record · Linux
The Linux kernel's RDMA/irdma driver can deadlock during a network-device reset. This occurs when a user initiates the reset while RDMA applications have active connections in iWARP mode, causing an indefinite wait during device removal.
Operators running Linux kernels with the RDMA/irdma driver should check their kernel vendor's advisory; affected versions were not provided.