xprtrdma: Check frwr_wp_create() during connect
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 21037b8c2258ec40de3b31be9ced43ceb3b784f7 · < 0f13fc7c7d2e0427517e63c739277a4cd338b0c5| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
xprtrdma: Check frwr_wp_create() during connect
frwr_wp_create() creates the singleton Memory Region used to encode padding for Write chunks whose payload length is not XDR-aligned. Its failure paths return a negative errno and leave ep->re_write_pad_mr set to NULL.
rpcrdma_xprt_connect() currently ignores that return value. If frwr_wp_create() fails after the rest of the connection setup succeeds, xprt_rdma_connect_worker() treats the connection attempt as successful and sets XPRT_CONNECTED. A later NFS/RDMA read with a non-4-byte-aligned receive page length reaches rpcrdma_encode_write_list(), passes the NULL write-pad MR to encode_rdma_segment(), and dereferences it.
This is locally triggerable on an NFS/RDMA client after a connect or reconnect hits a local MR allocation, DMA-map, MR-map, or post-send failure; a remote peer alone cannot force the local MR setup failure.
Check the return value and fail the connect as -ENOTCONN, matching the adjacent setup failures. This keeps XPRT_CONNECTED clear and lets the normal reconnect path retry.
From the CVE record · Linux
The Linux kernel's xprtrdma connection path can report success even when creation of a write-padding Memory Region fails. On an NFS/RDMA client, a subsequent read with a non-4-byte-aligned receive page length can dereference a NULL pointer. This is locally triggerable after a local setup failure; a remote peer alone cannot force that failure.
Engineers running Linux NFS/RDMA clients should check their kernel; affected versions are not specified.