Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64268, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.71% · top 46% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 8b6a361b8c482f22ac99c3273285ff16b23fba91 – < a31b6d18ded3cc32d9ee85a6ff0726d4274887b2
    • affected 8b6a361b8c482f22ac99c3273285ff16b23fba91 – < 595e6537ad1a210da32cbb9a7f91aa73090915ba
    • affected 8b6a361b8c482f22ac99c3273285ff16b23fba91 – < 3ef7e052cbd05a8b13a51a07b185a39ec93ee1cf
    • affected 8b6a361b8c482f22ac99c3273285ff16b23fba91 – < b2e26c955f8dd7e8d3f16c858db05245ea4fa817
    • affected 8b6a361b8c482f22ac99c3273285ff16b23fba91 – < 6bc89f34a4597f9f6d41f7a60c67a3153bfe8851
    • affected 8b6a361b8c482f22ac99c3273285ff16b23fba91 – < 423a78ff7928c2601013f73ec6d896f5597d0df5
    • affected 8b6a361b8c482f22ac99c3273285ff16b23fba91 – < 75c93cd3c421890f49ea93f0b978b9b7bb10e5e3
    • affected 8b6a361b8c482f22ac99c3273285ff16b23fba91 – < 7d29f7e9dbd844cae4d3e559cf78324b9642fd6b
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64268 badge
[![CVE-2026-64268](https://cveledger.app/badge/CVE-2026-64268.svg)](https://cveledger.app/cve/CVE-2026-64268)

Record last updated .