CVE-2026-45856

RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send

HIGH
7.1
CVSS Score
Published: May 27, 2026 at 12:15 PM UTC
Updated: October 19, 2026 at 08:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.0 ≤ v < 5.10.2525.11 ≤ v < 5.15.2025.16 ≤ v < 6.1.1656.13 ≤ v < 6.18.146.19 ≤ v < 6.19.46.2 ≤ v < 6.6.1286.7 ≤ v < 6.12.755.0c3bea3d2dc5358e05541527283279102383b0231
Vendor states this is fixed in 01c9b152647dc70dc06a4a2eff86ebb3b3c76075 (fixed)
Vendor states this is fixed in 1956f0a74ccf5dc9c3ef717f2985c3ed3400aab0 (fixed)
Vendor states this is fixed in 9b5ac1c15334d46c0dbd49d64a2257b929500163 (fixed)
Vendor states this is fixed in 9c15ec4cd4e7f57c6bbcb4e73e99290f150dd2a7 (fixed)
Vendor states this is fixed in bef70ff9841990658610512b4a18e4a88c9b4df6 (fixed)
Vendor states this is fixed in bf1feed1a7886af945f92890493aefd2b5c9928a (fixed)
Vendor states this is fixed in bf4454da8b1e712714628c0a0d6e7845bb40790a (fixed)
Vendor states this is fixed in d533425ac1f2925b4fc3e4ed9b9d72362cb23475 (fixed)
Vendor states this is fixed in 5.0 (unaffected)
Vendor states this is fixed in 5.10.252 (unaffected)
Vendor states this is fixed in 5.15.202 (unaffected)
Vendor states this is fixed in 6.1.165 (unaffected)
Vendor states this is fixed in 6.12.75 (unaffected)
Vendor states this is fixed in 6.18.14 (unaffected)
Vendor states this is fixed in 6.19.4 (unaffected)
Vendor states this is fixed in 6.6.128 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card