RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c3bea3d2dc5358e05541527283279102383b0231 · < bf4454da8b1e712714628c0a0d6e7845bb40790a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send
ib_uverbs_post_send() uses cmd.wqe_size from userspace without any validation before passing it to kmalloc() and using the allocated buffer as struct ib_uverbs_send_wr.
If a user provides a small wqe_size value (e.g., 1), kmalloc() will succeed, but subsequent accesses to user_wr->opcode, user_wr->num_sge, and other fields will read beyond the allocated buffer, resulting in an out-of-bounds read from kernel heap memory. This could potentially leak sensitive kernel information to userspace.
Additionally, providing an excessively large wqe_size can trigger a WARNING in the memory allocation path, as reported by syzkaller.
This is inconsistent with ib_uverbs_unmarshall_recv() which properly validates that wqe_size >= sizeof(struct ib_uverbs_recv_wr) before proceeding.
Add the same validation for ib_uverbs_post_send() to ensure wqe_size is at least sizeof(struct ib_uverbs_send_wr).
From the CVE record · Linux
The Linux kernel's ib_uverbs_post_send() does not validate a userspace-supplied wqe_size before allocating and reading a buffer. A local user who supplies a value that is too small can trigger an out-of-bounds kernel heap read that could leak sensitive information; an excessively large value can trigger a memory-allocation warning.
Engineers running Linux kernels with RDMA/uverbs should check whether their kernel includes the fix; affected versions were not specified.