CVE 7.1 HIGH

RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send_CVE-2026-45856

7.1 / 10
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Description

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).

Basic Information

ID CVE-2026-45856
Source Linux
Published May 27, 2026 at 12:15
Modified May 30, 2026 at 10:45

Affected Product

Vendor Linux
Product Linux
Version c3bea3d2dc5358e05541527283279102383b0231
Affected Versions Linux Linux c3bea3d2dc5358e05541527283279102383b0231
Linux Linux c3bea3d2dc5358e05541527283279102383b0231
Linux Linux c3bea3d2dc5358e05541527283279102383b0231
Linux Linux c3bea3d2dc5358e05541527283279102383b0231
Linux Linux c3bea3d2dc5358e05541527283279102383b0231
Linux Linux c3bea3d2dc5358e05541527283279102383b0231
Linux Linux c3bea3d2dc5358e05541527283279102383b0231
Linux Linux c3bea3d2dc5358e05541527283279102383b0231
Linux Linux 5.0

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.