Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64268: RDMA/siw: bound Read Response placement to the RREAD length

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.71% (FIRST EPSS); higher than 53.9% of all records.
  • 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 3ef7e052cbd05a8b13a51a07b185a39ec93ee1cf, 423a78ff7928c2601013f73ec6d896f5597d0df5, 595e6537ad1a210da32cbb9a7f91aa73090915ba; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.

Low priority for now. Upgrade to Linux Linux 3ef7e052cbd05a8b13a51a07b185a39ec93ee1cf, 423a78ff7928c2601013f73ec6d896f5597d0df5, 595e6537ad1a210da32cbb9a7f91aa73090915ba; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-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/siw: bound Read Response placement to the RREAD length In drivers/infiniband/sw/siw/siw_qp_rx.c, siw_proc_rresp() places each inbound Read Response DDP segment at sge->laddr + wqe->processed and then accumulates wqe->processed, but it never checks the running total against the sink buffer length on continuation segments. siw_check_sge() resolves and validates the sink memory only on the first fragment (the if (!*mem) branch), and siw_rresp_check_ntoh() compares the cumulative length against wqe->bytes only on the final segment (the !frx->more_ddp_segs guard). A connected siw peer that answers an outstanding RREAD with Read Response segments that keep the DDP Last flag clear, carrying more total payload than the RREAD requested, drives wqe->processed past the validated sink buffer; the next siw_rx_data() call writes out of bounds at sge->laddr + wqe->processed. siw runs iWARP over ordinary routable TCP, so the peer is the remote end of an established RDMA connection and needs no local privilege. Bound every segment before placement, exactly as siw_proc_send() and siw_proc_write() already do for their tagged and untagged paths, and terminate the connection with a base-or-bounds DDP error when the Read Response would overrun the sink buffer. This is the second receive-path length fix for this file. A separate change rejects an MPA FPDU length that underflows the per-fragment remainder in the header decode; that guard does not cover this case, because here each individual segment length is self-consistent and only the accumulated placement offset overruns the buffer.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Jul 25, 2026
Updated
Oct 19, 2026
EPSS
0.7% · 53th 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.7%

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-64268

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.261
  • linux linux kernel5.11 and later · before 5.15.212
  • linux linux kernel5.16 and later · before 6.1.178
  • linux linux kernel6.2 and later · before 6.6.145
  • linux linux kernel6.7 and later · before 6.12.96
  • linux linux kernel6.13 and later · before 6.18.39
  • linux linux kernel6.19 and later · before 7.1.4

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 a31b6d18ded3cc32d9ee85a6ff0726d4274887b2affected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 595e6537ad1a210da32cbb9a7f91aa73090915baaffected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 3ef7e052cbd05a8b13a51a07b185a39ec93ee1cfaffected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before b2e26c955f8dd7e8d3f16c858db05245ea4fa817affected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 6bc89f34a4597f9f6d41f7a60c67a3153bfe8851affected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 423a78ff7928c2601013f73ec6d896f5597d0df5affected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 75c93cd3c421890f49ea93f0b978b9b7bb10e5e3affected · git
    • 8b6a361b8c482f22ac99c3273285ff16b23fba91 and later · before 7d29f7e9dbd844cae4d3e559cf78324b9642fd6baffected · 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.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.159.1.el8_104.18.0-553.159.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.159.1.rt7.500.el8_104.18.0-553.159.1.rt7.500.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.159.1.rt7.500.el8_104.18.0-553.159.1.rt7.500.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.159.1.rt7.500.el8_104.18.0-553.159.1.rt7.500.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.159.1.rt7.500.el8_104.18.0-553.159.1.rt7.500.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.159.1.rt7.500.el8_104.18.0-553.159.1.rt7.500.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.159.1.rt7.500.el8_104.18.0-553.159.1.rt7.500.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.159.1.rt7.500.el8_104.18.0-553.159.1.rt7.500.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.159.1.rt7.500.el8_104.18.0-553.159.1.rt7.500.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.159.1.rt7.500.el8_104.18.0-553.159.1.rt7.500.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-64256Jul 25, 2026 · xfs: don't wrap around quota ids in dqiterate
    22Monitor
  • ← EarlierCVE-2026-64266Jul 25, 2026 · fuse: re-lock request before returning from fuse_ref_folio()
    31Monitor
  • Later →CVE-2026-64270Jul 25, 2026 · Input: mms114 - reject an oversized device packet size
    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 Linux3ef7e052cbd05a8b13a51a07b185a39ec93ee1cfVendor (CNA)
Linux Linux423a78ff7928c2601013f73ec6d896f5597d0df5Vendor (CNA)
Linux Linux595e6537ad1a210da32cbb9a7f91aa73090915baVendor (CNA)
Linux Linux6bc89f34a4597f9f6d41f7a60c67a3153bfe8851Vendor (CNA)
Linux Linux75c93cd3c421890f49ea93f0b978b9b7bb10e5e3Vendor (CNA)
Linux Linux7d29f7e9dbd844cae4d3e559cf78324b9642fd6bVendor (CNA)
Linux Linuxa31b6d18ded3cc32d9ee85a6ff0726d4274887b2Vendor (CNA)
Linux Linuxb2e26c955f8dd7e8d3f16c858db05245ea4fa817Vendor (CNA)
azl3 kernel 6.6.144.1-1 on Azure Linux 3.06.6.145.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.159.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.159.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.159.1.rt7.500.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.159.1.rt7.500.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.159.1.rt7.500.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.159.1.rt7.500.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.159.1.rt7.500.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.159.1.rt7.500.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.159.1.rt7.500.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.159.1.rt7.500.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.159.1.rt7.500.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.159.1.rt7.500.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.159.1.rt7.500.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.159.1.rt7.500.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.159.1.rt7.500.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.159.1.rt7.500.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.159.1.rt7.500.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.159.1.rt7.500.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.159.1.rt7.500.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)

+7

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-787 · Out-of-bounds Write

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.

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

Change log

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

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

References

All records