CVE-2026-64269

In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg When the server answers an RTRS READ, rdma_write_sg() builds the source scatter/gather entry for the IB_WR_RDMA_WRITE that returns data to the peer. Its length is taken directly from the wire descriptor: plist->length = le32_to_cpu(id->rd_msg->desc[0].len); rd_msg points into the chunk buffer that the remote peer filled via RDMA-WRITE-WITH-IMM (rtrs_srv_rdma_done() -> process_io_req() -> process_read()), so desc[0].len is attacker-controlled and, before this change, was only rejected when zero. The source address is the fixed chunk start (dma_addr[msg_id]) and the source lkey is the PD-wide local_dma_lkey, which is not tied to the chunk's MR mapping, so the verbs layer does not constrain the transfer length to max_chunk_size. msg_id and off are bounded against queue_depth and max_chunk_size in rtrs_srv_rdma_done(), but desc[0].len is a separate field that was not checked against the chunk size. A peer that advertises desc[0].len larger than max_chunk_size can make the posted RDMA write read past the chunk's mapped region. The resulting behaviour depends on the IOMMU configuration: with no IOMMU or in passthrough mode the read may extend into memory adjacent to the chunk and be returned to the peer, which can disclose host memory; with a translating IOMMU the out-of-range access is expected to fault and abort the connection. In either case the transfer exceeds what the protocol permits and is driven by a remote peer. Reject a descriptor length above max_chunk_size, mirroring the existing off >= max_chunk_size bound in rtrs_srv_rdma_done(). Legitimate clients do not exceed it: the client sets desc[0].len to its MR length, which is capped at the negotiated max_io_size (max_chunk_size - MAX_HDR_SIZE).

• https://git.kernel.org/stable/c/2912f3d40355dabc08fdbaaf2764d02445fe88dcPatch
• https://git.kernel.org/stable/c/5a45d0aa1fa50a333ce5763ade744e2d89838667Patch
• https://git.kernel.org/stable/c/68c09762172f6224e9ddf9b0a60bacbb36e443ebPatch
• https://git.kernel.org/stable/c/6cada540150894e81042a0ae0c796a21a9a877daPatch
• https://git.kernel.org/stable/c/6f40246f4312fdbab5a13cc440adebf95eb2aa66Patch
• https://git.kernel.org/stable/c/963af8d97a8c6a117134a8d0db1415e0489200b1Patch
• https://git.kernel.org/stable/c/a35b7a8728a53ddc80b323970689fa5985816836
• https://git.kernel.org/stable/c/da3e44add94b05dfde56f898421922f5cf35705fPatch

Published

Jul 25, 2026

Last Modified

Aug 23, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-64263In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-64264In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-64265In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64266In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64267In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-64268In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-6427The a3 Lazy Load plugin for WordPress is vulnerable to Store…6.4
• CVE-2026-64270In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64271In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64272In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64273In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64274In the Linux kernel, the following vulnerability has been re…7.8