Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1371ef6b1ecf3676b8942f5dfb3634fb0648128e, 205955f29c26330b1dc7fdeadd5bb97c38e26f56, 362e45fd9069ffa1523f9f1633b606ebf72060d7; azl3 kernel 6.6.126.1-1 on Azure Linux 3.0 6.6.130.1-1.

Low priority for now. Upgrade to Linux Linux 1371ef6b1ecf3676b8942f5dfb3634fb0648128e, 205955f29c26330b1dc7fdeadd5bb97c38e26f56, 362e45fd9069ffa1523f9f1633b606ebf72060d7; azl3 kernel 6.6.126.1-1 on Azure Linux 3.0 6.6.130.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Mar 18, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23243

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.24.1 and later · before 5.10.252
  • linux linux kernel5.11 and later · before 5.15.202
  • linux linux kernel5.16 and later · before 6.1.165
  • linux linux kernel6.2 and later · before 6.6.128
  • linux linux kernel6.7 and later · before 6.12.75
  • linux linux kernel6.13 and later · before 6.18.14
  • linux linux kernel6.19 and later · before 6.19.4
  • linux linux kernel2.6.24

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.24affected
    • 2be8e3ee8efd6f99ce454115c29d09750915021a and later · before 1371ef6b1ecf3676b8942f5dfb3634fb0648128eaffected · git
    • 2be8e3ee8efd6f99ce454115c29d09750915021a and later · before 362e45fd9069ffa1523f9f1633b606ebf72060d7affected · git
    • 2be8e3ee8efd6f99ce454115c29d09750915021a and later · before 6eb2919474ca105c5b13d19574e25f0ddcf19ca2affected · git
    • 2be8e3ee8efd6f99ce454115c29d09750915021a and later · before a6a3e4af10993cb9e4b8f0548680aba0ab5f3b0daffected · git
    • 2be8e3ee8efd6f99ce454115c29d09750915021a and later · before 9c80d688f402539dfc8f336de1380d6b4ee14316affected · git
    • 2be8e3ee8efd6f99ce454115c29d09750915021a and later · before 205955f29c26330b1dc7fdeadd5bb97c38e26f56affected · git
    • 2be8e3ee8efd6f99ce454115c29d09750915021a and later · before 52ab82cc5cf8ada5c3fb6ffe8f32fdb2fc27a34baffected · git
    • 2be8e3ee8efd6f99ce454115c29d09750915021a and later · before 5551b02fdbfd85a325bb857f3a8f9c9f33397ed2affected · git
    • before 2.6.24not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.126.1.el8_104.18.0-553.126.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.126.1.rt7.467.el8_104.18.0-553.126.1.rt7.467.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.126.1.rt7.467.el8_104.18.0-553.126.1.rt7.467.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.126.1.rt7.467.el8_104.18.0-553.126.1.rt7.467.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.126.1.rt7.467.el8_104.18.0-553.126.1.rt7.467.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.126.1.rt7.467.el8_104.18.0-553.126.1.rt7.467.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.126.1.rt7.467.el8_104.18.0-553.126.1.rt7.467.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.126.1.rt7.467.el8_104.18.0-553.126.1.rt7.467.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.126.1.rt7.467.el8_104.18.0-553.126.1.rt7.467.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.126.1.rt7.467.el8_104.18.0-553.126.1.rt7.467.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-71267Mar 18, 2026 · fs: ntfs3: fix infinite loop triggered by zero-sized ATTR_LIST
    22Monitor
  • ← EarlierCVE-2026-23242Mar 18, 2026 · RDMA/siw: Fix potential NULL pointer dereference in header processing
    30Monitor
  • Later →CVE-2026-23245Mar 18, 2026 · net/sched: act_gate: snapshot parameters with RCU on replace
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1371ef6b1ecf3676b8942f5dfb3634fb0648128eVendor (CNA)
Linux Linux205955f29c26330b1dc7fdeadd5bb97c38e26f56Vendor (CNA)
Linux Linux362e45fd9069ffa1523f9f1633b606ebf72060d7Vendor (CNA)
Linux Linux52ab82cc5cf8ada5c3fb6ffe8f32fdb2fc27a34bVendor (CNA)
Linux Linux5551b02fdbfd85a325bb857f3a8f9c9f33397ed2Vendor (CNA)
Linux Linux6eb2919474ca105c5b13d19574e25f0ddcf19ca2Vendor (CNA)
Linux Linux9c80d688f402539dfc8f336de1380d6b4ee14316Vendor (CNA)
Linux Linuxa6a3e4af10993cb9e4b8f0548680aba0ab5f3b0dVendor (CNA)
azl3 kernel 6.6.126.1-1 on Azure Linux 3.06.6.130.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-687.5.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.5.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.5.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.5.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.5.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.5.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.5.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.5.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.5.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.5.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.5.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.5.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:5.14.0-70.178.1.el9_0 · Red Hat:rhel_e4s:9.0::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-70.178.1.el9_0 · Red Hat:rhel_e4s:9.0::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-70.178.1.el9_0 · Red Hat:rhel_e4s:9.0::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-70.178.1.el9_0 · Red Hat:rhel_e4s:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-70.178.1.el9_0 · Red Hat:rhel_e4s:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-70.178.1.el9_0 · Red Hat:rhel_e4s:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-70.178.1.el9_0 · Red Hat:rhel_e4s:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-s390x0:5.14.0-70.178.1.el9_0 · Red Hat:rhel_e4s:9.0::appstreamPackage registry (OSV)

+18

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records