RDMA/mad: Fix receive buffer leak when PKey enforcement fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 47a2b338fe63200d716d2e24131cdb49f17c77da · < 5091e25ec503f7fc02723ca435226467b68caac7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
RDMA/mad: Fix receive buffer leak when PKey enforcement fails
ib_mad_complete_recv() initializes mad_recv_wc->rmpp_list and then runs ib_mad_enforce_security() before linking recv_buf onto that list. On failure it calls ib_free_recv_mad(), which only walks rmpp_list and frees the ib_mad_private of every buffer found there. As the list is still empty at that point, nothing is freed at all.
The caller cannot clean up either: ib_mad_recv_done() sets recv to NULL right after ib_mad_complete_recv() returns, assuming the MAD layer took ownership of the buffer. Every MAD that fails the PKey check therefore leaks one ib_mad_private (about 300 bytes per IB port MAD, ~2K for OPA), and a remote node can trigger this repeatedly by sending MADs with a wrong PKey.
Link recv_buf onto rmpp_list right after the list is initialized, so the error path has something to free.
From the CVE record · Linux
The Linux kernel’s RDMA/mad receive path leaks a buffer when a MAD fails PKey enforcement. A remote node can repeatedly send MADs with the wrong PKey to trigger the leak; no user interaction is required.
Engineers running Linux kernels with RDMA/mad support should check whether their kernel includes this fix; affected versions were not specified.