RDMA/rxe: Reject unknown opcodes before ICRC processing
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8700e3e7c4857d28ebaa824509934556da0b3e76 · < 006a3a5f75345c6a0dbf13fd3ee01406e93b6733| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
RDMA/rxe: Reject unknown opcodes before ICRC processing
Even after applying commit 7244491dab34 ("RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv"), a single unauthenticated UDP packet can still trigger panic. That patch handled payload_size() underflow only for valid opcodes with short packets, not for packets carrying an unknown opcode. The unknown-opcode OOB read described below predates that commit and reaches back to the initial Soft RoCE driver.
The check added there reads
pkt->paylen < header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE
where header_size(pkt) expands to rxe_opcode[pkt->opcode].length. The rxe_opcode[] array has 256 entries but is only populated for defined IB opcodes; any other entry (for example opcode 0xff) is zero-initialized, so length == 0 and the check degenerates to
pkt->paylen < 0 + bth_pad(pkt) + RXE_ICRC_SIZE
which does not constrain pkt->paylen enough. rxe_icrc_hdr() then computes
From the CVE record · Linux
The Linux kernel’s RDMA/rxe driver can read beyond a packet buffer when processing an unknown opcode. A single unauthenticated UDP packet can trigger a kernel panic over the network when a Soft RoCE link is configured; no connection or user interaction is needed.
Operators running Linux kernels with the RDMA/rxe driver and a configured Soft RoCE link should check their systems; affected versions are not specified.