All Threat Alerts
criticalCVE Alert
CVE-2026-64269

Critical Vulnerability: CVE-2026-64269 โ€” linux โ€” linux_kernel

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_

Thursday, August 13, 2026linuxVulnios Threat Intelligence
Share:

Vulnerability Snapshot

CVE-2026-64269 is rated CRITICAL โ€” exploitation is trivial or already observed in the wild and impact is severe. Patch immediately, not on the next maintenance window.

Affected technology: linux_kernel.

Executive Summary

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

Why It Matters

CVE-2026-64269 is rated CRITICAL severity, requiring immediate attention from security teams.

CVSS Base Score: 9.1/10

EPSS (Exploit Prediction): 0.7% probability of exploitation in the next 30 days.

Affected Technologies

Vendors: linux

Products: linux_kernel

๐Ÿ›ก๏ธWhat Defenders Should Check

  • Check if you are affected โ€” Review your asset inventory for products listed in CVE-2026-64269.
  • Apply available patches โ€” Visit vendor advisories for the latest security updates.
  • Monitor for exploitation โ€” Check your SIEM/IDS logs for related indicators.
  • Use Vulnios to continuously monitor your exposure to CVE-2026-64269 and similar vulnerabilities.

    References & Sources

    How Vulnios Detects This

    Vulnios scans for this vulnerability using Trivy and Grype for CVE matching against your container images and OS package manifests. Run a scan against your environment to see whether you are exposed; findings are linked back to the original CVE record so triage starts with the patch path already known.

    AI Security Advisor

    Powered by Gemini

    Get AI-powered security recommendations tailored to this specific threat โ€” including risk assessment, detection guidance, MITRE ATT&CK mapping, and actionable remediation steps.

    Affected Products

    linux_kernel

    Sources

    Related Threat Alerts

    Frequently Asked Questions

    What is CVE-2026-64269?

    CVE-2026-64269 is a critical-severity vulnerability tracked under the Common Vulnerabilities and Exposures program. 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

    Am I affected?

    Check whether your environment runs linux_kernel. If you operate any of those, treat yourself as in scope until you have evidence otherwise. A Vulnios scan will identify the exact assets carrying the affected version.

    How urgent is the response?

    Critical: do not wait for your normal patch cycle. Verify exposure today, apply the vendor patch immediately, and add detection rules for any post-exploit indicators.

    How do I remediate?

    Apply the vendor patch listed in the upstream advisory linked under Sources. If the patch is not yet available, follow the vendor-supplied workaround (often a config flag or feature disable) and add detections for the published exploit pattern in your SIEM. Re-scan after the patch lands to confirm the finding clears.

    Where can I track exploitation activity?

    Watch CISA's Known Exploited Vulnerabilities catalog for CVE-2026-64269. Cross-reference with public exploit databases and your own SIEM/IDS for indicator-of-compromise patterns. Vulnios tracks KEV status automatically and surfaces it on the asset findings view.

    How does Vulnios help with this?

    Vulnios continuously cross-references your asset inventory against the live CVE feed (NVD, vendor advisories, CISA KEV, and curated OSINT). When a new CVE matches your environment, you get a prioritized finding with the severity, KEV status, exploit-prediction (EPSS), and a direct path to the vendor patch. You can start a free scan from the homepage.

    critical

    Protect Your Organization

    Monitor CVEs, scan for vulnerabilities, and get real-time threat alerts โ€” all in one platform.

    Get instant alerts on Telegram

    Join our public channel for real-time critical CVE alerts.

    Follow @vulnios