Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64102: RDMA/siw: Reject MPA FPDU length underflow before signed receive math

Noroxi assessment

Priority: Monitor (action score 39/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.50% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 0ce1bc9e46ecabe84772bb561e373c0d9876d6f2, 1012896f4225e8f801ff3c1648023845b66dfb11, 14553be882d9ce91749c9d64041de66e34ad8e70.

Low priority for now. Upgrade to Linux Linux 0ce1bc9e46ecabe84772bb561e373c0d9876d6f2, 1012896f4225e8f801ff3c1648023845b66dfb11, 14553be882d9ce91749c9d64041de66e34ad8e70 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/siw: Reject MPA FPDU length underflow before signed receive math A malicious connected siw peer can send an iWARP FPDU whose MPA length field (c_hdr->mpa_len, 16 bit big-endian, peer-controlled) is smaller than the fixed DDP/RDMAP header for the announced opcode. Soft-iWARP parses the full header in siw_get_hdr() based on iwarp_pktinfo[opcode] .hdr_len, but never compares mpa_len against that header length. siw_tcp_rx_data() then derives srx->fpdu_part_rem = be16_to_cpu(mpa_len) - fpdu_part_rcvd + MPA_HDR_SIZE; where fpdu_part_rcvd equals iwarp_pktinfo[opcode].hdr_len at this point. For a tagged WRITE (hdr_len 16, MPA_HDR_SIZE 2) the smallest on-wire mpa_len of 0 yields fpdu_part_rem = -14, and any mpa_len below hdr_len - MPA_HDR_SIZE underflows to a negative int. The signed value then flows into siw_proc_write()/siw_proc_rresp() as bytes = min(srx->fpdu_part_rem, srx->skb_new); is handed to siw_check_mem() as an int len (whose interval check addr + len > mem->va + mem->len is satisfied for a valid base when len is negative), and reaches siw_rx_data() -> siw_rx_kva() / siw_rx_umem() -> skb_copy_bits() as a signed copy length. The header copy branch in skb_copy_bits() promotes that to size_t, producing a multi-gigabyte read. KASAN under a KUnit harness that drives the real kernel TCP receive path -- a loopback AF_INET socketpair, the malformed FPDU written via kernel_sendmsg, sk_data_ready firing in softirq, tcp_read_sock dispatching to siw_tcp_rx_data -- reports: BUG: KASAN: use-after-free in skb_copy_bits+0x284/0x480 Read of size 4294967295 at addr ffff888... Call Trace: skb_copy_bits siw_rx_kva siw_rx_data siw_check_mem siw_proc_write siw_tcp_rx_data __tcp_read_sock siw_qp_llp_data_ready tcp_data_ready tcp_data_queue Add the missing invariant at the earliest point where the peer header is fully assembled. iwarp_pktinfo[*].hdr_len - MPA_HDR_SIZE is exactly the value the siw transmitter uses as the minimum mpa_len for each opcode (drivers/infiniband/sw/siw/siw_qp.c:33), so this matches the protocol contract. Out-of-range FPDUs terminate the connection with TERM_ERROR_LAYER_LLP / LLP_ETYPE_MPA / LLP_ECODE_FPDU_START -- which is RFC 5044 Section 8 error code 3 ("Marker and ULPDU Length fields do not agree on the start of an FPDU"), the correct framing-error class for this inconsistency.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Jul 19, 2026
Updated
Oct 19, 2026
EPSS
0.5% · 42th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.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-64102

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 kernel5.3 and later · before 5.10.258
  • linux linux kernel5.11 and later · before 5.15.209
  • linux linux kernel5.16 and later · before 6.1.175
  • linux linux kernel6.2 and later · before 6.6.142
  • linux linux kernel6.7 and later · before 6.12.92
  • linux linux kernel6.13 and later · before 6.18.34
  • linux linux kernel6.19 and later · before 7.0.11
  • linux linux kernel7.1

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

    • 5.3affected
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 683f7cfbf514193d63c0efa079f3352bde84c2e0affected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 4a331582011d9e8089af8aa2a61ec6b4443bb245affected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 33a8b5e971e294ec2a7b74211c545e09efd8e9acaffected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 14553be882d9ce91749c9d64041de66e34ad8e70affected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before c7c0c0f4379dedec12d24dbb9dded5d2db7fd9f2affected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 1012896f4225e8f801ff3c1648023845b66dfb11affected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 775b4dc9618a99a1fa48b57554041a5dc17e1336affected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 0ce1bc9e46ecabe84772bb561e373c0d9876d6f2affected · git
    • before 5.3not 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.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.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-2026-64097Jul 19, 2026 · drm/amd/display: Validate GPIO pin LUT table size before iterating
    31Monitor
  • ← EarlierCVE-2026-64098Jul 19, 2026 · drm/virtio: use uninterruptible resv lock for plane updates
    31Monitor
  • Later →CVE-2026-64106Jul 19, 2026 · KVM: arm64: vgic-its: Reject restored DTE with out-of-range num_eventid_bits
    36Monitor

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 Linux0ce1bc9e46ecabe84772bb561e373c0d9876d6f2Vendor (CNA)
Linux Linux1012896f4225e8f801ff3c1648023845b66dfb11Vendor (CNA)
Linux Linux14553be882d9ce91749c9d64041de66e34ad8e70Vendor (CNA)
Linux Linux33a8b5e971e294ec2a7b74211c545e09efd8e9acVendor (CNA)
Linux Linux4a331582011d9e8089af8aa2a61ec6b4443bb245Vendor (CNA)
Linux Linux683f7cfbf514193d63c0efa079f3352bde84c2e0Vendor (CNA)
Linux Linux775b4dc9618a99a1fa48b57554041a5dc17e1336Vendor (CNA)
Linux Linuxc7c0c0f4379dedec12d24dbb9dded5d2db7fd9f2Vendor (CNA)
almalinux:kernel5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+5

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

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • 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
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/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.

ATT&CK techniques

—

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

All records