CVE-2026-45856

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. the CNA's CVSS baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 5 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jun 12, 2026
No patch confirmed yet.
generic

RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d533425ac1f2925b4fc3e4ed9b9d72362cb23475
generic

RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bf4454da8b1e712714628c0a0d6e7845bb40790a
generic

RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bf1feed1a7886af945f92890493aefd2b5c9928a
generic

RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bef70ff9841990658610512b4a18e4a88c9b4df6
generic

RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c15ec4cd4e7f57c6bbcb4e73e99290f150dd2a7
generic

RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9b5ac1c15334d46c0dbd49d64a2257b929500163
generic

RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1956f0a74ccf5dc9c3ef717f2985c3ed3400aab0
generic

RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01c9b152647dc70dc06a4a2eff86ebb3b3c76075

Vendor Advisories for CVE-2026-45856(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-09-14ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-134.134.1~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-09-14ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-09-14ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-09-14ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-09-14ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-09-14ubuntu
linuxKernel @ 5.10.252osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(24)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 257 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 09:22 UTCEG score recompute
  3. 2026-09-14 09:22 UTCVendor advisory
  4. 2026-09-14 09:21 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-13 04:09 UTCOSV refresh
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 05:52 UTCEG score recompute
  24. 2026-08-25 05:52 UTCVendor advisory
  25. 2026-08-25 05:52 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 15:40 UTCEG score recompute
  2. 2026-08-23 15:40 UTCVendor advisory
  3. 2026-08-23 15:39 UTCGHSA enrichment
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 21:01 UTCEG score recompute
  7. 2026-08-21 21:01 UTCVendor advisory
  8. 2026-08-21 21:01 UTCGHSA enrichment
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 17:46 UTCEG score recompute
  11. 2026-08-20 17:46 UTCVendor advisory
  12. 2026-08-20 17:46 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 09:22 UTCVendor advisory
  17. 2026-08-17 09:22 UTCGHSA enrichment
  18. 2026-08-16 16:27 UTCEG score recompute
  19. 2026-08-16 16:27 UTCVendor advisory
  20. 2026-08-16 16:27 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:56 UTCEG score recompute
  23. 2026-08-16 02:56 UTCVendor advisory
  24. 2026-08-16 02:56 UTCGHSA enrichment
  25. 2026-08-16 02:14 UTCEPSS rescore
  26. 2026-08-15 02:58 UTCEG score recompute
  27. 2026-08-15 02:58 UTCVendor advisory
  28. 2026-08-15 02:58 UTCGHSA enrichment
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 14:04 UTCVendor advisory
  31. 2026-08-14 14:04 UTCGHSA enrichment
  32. 2026-08-14 01:35 UTCEG score recompute
  33. 2026-08-14 01:35 UTCVendor advisory
  34. 2026-08-14 01:35 UTCGHSA enrichment
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 03:06 UTCVendor advisory
  37. 2026-08-13 03:06 UTCGHSA enrichment
  38. 2026-08-12 14:37 UTCEG score recompute
  39. 2026-08-12 14:37 UTCVendor advisory
  40. 2026-08-12 14:37 UTCGHSA enrichment
  41. 2026-08-12 13:51 UTCEPSS rescore
  42. 2026-08-12 02:06 UTCEG score recompute
  43. 2026-08-12 02:06 UTCVendor advisory
  44. 2026-08-12 02:06 UTCGHSA enrichment
  45. 2026-08-11 13:37 UTCVendor advisory
  46. 2026-08-11 13:37 UTCGHSA enrichment
  47. 2026-08-11 00:15 UTCEG score recompute
  48. 2026-08-11 00:15 UTCVendor advisory
  49. 2026-08-11 00:15 UTCGHSA enrichment
  50. 2026-08-11 00:00 UTCEPSS rescore
  51. 2026-08-10 11:44 UTCVendor advisory
  52. 2026-08-10 11:44 UTCGHSA enrichment
  53. 2026-08-09 23:13 UTCEG score recompute
  54. 2026-08-09 23:13 UTCVendor advisory
  55. 2026-08-09 23:13 UTCGHSA enrichment
  56. 2026-08-09 13:46 UTCEPSS rescore
  57. 2026-08-09 10:44 UTCVendor advisory
  58. 2026-08-09 10:44 UTCGHSA enrichment
  59. 2026-08-08 22:04 UTCEG score recompute
  60. 2026-08-08 22:04 UTCVendor advisory
  61. 2026-08-08 22:04 UTCGHSA enrichment
  62. 2026-08-08 16:37 UTCEPSS rescore
  63. 2026-08-08 04:34 UTCEG score recompute
  64. 2026-08-08 04:34 UTCVendor advisory
  65. 2026-08-08 04:34 UTCGHSA enrichment
  66. 2026-08-07 16:06 UTCVendor advisory
  67. 2026-08-07 16:06 UTCGHSA enrichment
  68. 2026-08-07 03:36 UTCVendor advisory
  69. 2026-08-07 03:36 UTCGHSA enrichment
  70. 2026-08-06 14:59 UTCEG score recompute
  71. 2026-08-06 14:59 UTCVendor advisory
  72. 2026-08-06 14:59 UTCGHSA enrichment
  73. 2026-08-06 13:47 UTCEPSS rescore
  74. 2026-08-06 02:12 UTCEG score recompute
  75. 2026-08-06 02:12 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-45856?
CVE-2026-45856 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/uverbs: Validate wqesize before using it in ibuverbspostsend ibuverbspostsend() uses cmd.wqesize from userspace without any validation before passing it to kmalloc() and using the allocated buffer as struct ibuverbssend_wr. If…
When was CVE-2026-45856 disclosed?
CVE-2026-45856 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45856 actively exploited?
CVE-2026-45856 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.0% of all scored CVEs.
What is the CVSS score of CVE-2026-45856?
CVE-2026-45856 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-45856?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45856, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45856

Explore →

Is Your Infrastructure Affected by CVE-2026-45856?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.