RDMA/erdma: complete object teardown when the destroy command fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 155055771704f8cbb5c176a4309b7dc30a50450c · < 652befcba956ef357f480525ccbe25c59bc81d4d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
RDMA/erdma: complete object teardown when the destroy command fails
erdma_destroy_qp(), erdma_destroy_cq(), erdma_dereg_mr(), and erdma_destroy_ah() returned early when erdma_post_cmd_wait() failed, leaking the queue buffers, MTTs, doorbells and the STAG, QPN, CQN and AHN identifiers. A command timeout clears ERDMA_CMDQ_STATE_OK_BIT and permanently disables the command queue, so no retry can succeed; the RDMA core keeps the object after a failed destructor and forced uverbs cleanup then nulls the pointers, making the resources unreachable.
Warn on failure but release every software-owned resource and return success, since during terminal destruction the hardware command result is only diagnostic.
From the CVE record · Linux
In the Linux kernel's RDMA/erdma component, a failed destroy command can leave queue buffers and other resources unreleased. This can exhaust resources; the input does not specify how an attacker could trigger the failure or whether network access, authentication, or user interaction is required.
Teams running Linux kernels with the RDMA/erdma component should check their versions; affected versions were not provided.