CVE-2026-23243

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
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.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

RDMA/umad: Reject negative data_len in ib_umad_write

ib_umad_write computes data_len from user-controlled count and the MAD header sizes. With a mismatched user MAD header size and RMPP header length, data_len can become negative and reach ib_create_send_mad(). This can make the padding calculation exceed the segment size and trigger an out-of-bounds memset in alloc_send_rmpp_list().

Add an explicit check to reject negative data_len before creating the send buffer.

KASAN splat: [ 211.363464] BUG: KASAN: slab-out-of-bounds in ib_create_send_mad+0xa01/0x11b0 [ 211.364077] Write of size 220 at addr ffff88800c3fa1f8 by task spray_thread/102 [ 211.365867] ib_create_send_mad+0xa01/0x11b0 [ 211.365887] ib_umad_write+0x853/0x1c80

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

March 18, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

RDMA/umad: Reject negative data_len in ib_umad_write - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/umad: Reject negative data_len in ib_umad_write - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/umad: Reject negative data_len in ib_umad_write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6eb2919474ca105c5b13d19574e25f0ddcf19ca2
generic

RDMA/umad: Reject negative data_len in ib_umad_write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5551b02fdbfd85a325bb857f3a8f9c9f33397ed2
generic

RDMA/umad: Reject negative data_len in ib_umad_write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52ab82cc5cf8ada5c3fb6ffe8f32fdb2fc27a34b
generic

RDMA/umad: Reject negative data_len in ib_umad_write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/362e45fd9069ffa1523f9f1633b606ebf72060d7
generic

RDMA/umad: Reject negative data_len in ib_umad_write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/205955f29c26330b1dc7fdeadd5bb97c38e26f56
generic

RDMA/umad: Reject negative data_len in ib_umad_write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1371ef6b1ecf3676b8942f5dfb3634fb0648128e

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-rt-0:3.10.0-1160.155.1.rt56.1307.el72026-07-17redhat
redhatkernel-0:3.10.0-1160.153.1.el72026-06-22redhat
redhatkernel-0:4.18.0-305.194.1.el8_42026-06-17redhat
redhatkernel-0:4.18.0-372.196.1.el8_62026-06-17redhat
redhatkernel-0:4.18.0-553.126.1.el8_102026-05-28redhat
redhatkernel-rt-0:4.18.0-553.126.1.rt7.467.el8_102026-05-28redhat
redhatkernel-0:5.14.0-427.127.1.el9_42026-05-27redhat
redhatkernel-0:5.14.0-284.172.1.el9_22026-05-26redhat
redhatkernel-rt-0:5.14.0-284.172.1.rt14.457.el9_22026-05-20redhat
redhatkernel-0:4.18.0-477.143.1.el8_82026-05-20redhat
redhatkernel-0:6.12.0-211.7.1.el10_22026-05-19redhat
redhatkernel-0:5.14.0-687.5.1.el9_82026-05-19redhat
redhatkernel-0:6.12.0-55.72.1.el10_02026-05-11redhat
redhatkernel-0:5.14.0-570.112.1.el9_62026-05-06redhat
redhatkernel-rt-0:5.14.0-70.178.1.rt21.250.el9_02026-05-06redhat
redhatkernel-0:5.14.0-70.178.1.el9_02026-05-06redhat
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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
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 (100 versions)6.18.14-1

Weakness Classification(1)

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

Additional Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 5× in last 7d / 72× 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 210 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23243?
CVE-2026-23243 is a high vulnerability published on March 18, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/umad: Reject negative datalen in ibumad_write ibumadwrite computes data_len from user-controlled count and the MAD header sizes. With a mismatched user MAD header size and RMPP header length, datalen can become negative and…
When was CVE-2026-23243 disclosed?
CVE-2026-23243 was first published in the National Vulnerability Database on March 18, 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-23243 actively exploited?
CVE-2026-23243 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-23243?
CVE-2026-23243 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-23243?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23243, 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-23243

Explore →

Is Your Infrastructure Affected by CVE-2026-23243?

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