SECUFOCUSNOW
Home›CVE index›CVE-2026-64102
Review reviewCritical

CVE-2026-64102

Linux

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

CVSS
9.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.20
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 9.8

Vulnerability overview

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

Affected product and versions

Product
Linux
Affected versions
>= 8b6a361b8c482f22ac99c3273285ff16b23fba91 < 683f7cfbf514193d63c0efa079f3352bde84c2e0, >= 8b6a361b8c482f22ac99c3273285ff16b23fba91 < 4a331582011d9e8089af8aa2a61ec6b4443bb245, >= 8b6a361b8c482f22ac99c3273285ff16b23fba91 < 33a8b5e971e294ec2a7b74211c545e09efd8e9ac, >= 8b6a361b8c482f22ac99c3273285ff16b23fba91 < 14553be882d9ce91749c9d64041de66e34ad8e70, >= 8b6a361b8c482f22ac99c3273285ff16b23fba91 < c7c0c0f4379dedec12d24dbb9dded5d2db7fd9f2, >= 8b6a361b8c482f22ac99c3273285ff16b23fba91 < 1012896f4225e8f801ff3c1648023845b66dfb11, >= 8b6a361b8c482f22ac99c3273285ff16b23fba91 < 775b4dc9618a99a1fa48b57554041a5dc17e1336, >= 8b6a361b8c482f22ac99c3273285ff16b23fba91 < 0ce1bc9e46ecabe84772bb561e373c0d9876d6f2, >= 5.3
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

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