Linux kernel vulnerability in RDMA server can disclose host memory or disrupt services; Linux is core infrastructure used across industries.
CVE-2026-64269
Linux kernel RDMA server accepts oversized RDMA-WRITE, can leak host memory or abort connections.
Is CVE-2026-64269 being exploited?
Not confirmed. CVE-2026-64269 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.71% probability of exploitation in the next 30 days.
How severe is CVE-2026-64269?
CVE-2026-64269 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64269?
Yes. A fix has been recorded for CVE-2026-64269. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64269 affect?
CVE-2026-64269 affects Linux kernel (rtrs / RDMA subsystem), Systems using RDMA/InfiniBand (HPC, storage, datacenter). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64269?
Apply vendor kernel patches immediately; block or isolate RDMA access if patching is delayed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote peer can force out-of-bounds RDMA read to disclose host memory or cause connection aborts; may enable data exfiltration or service disruption.
Immediate action required
- affected>= 9cb837480424e78ed585376f944088246685aec3 and < a35b7a8728a53ddc80b323970689fa5985816836
- affected>= 9cb837480424e78ed585376f944088246685aec3 and < 68c09762172f6224e9ddf9b0a60bacbb36e443eb
- affected>= 9cb837480424e78ed585376f944088246685aec3 and < 6cada540150894e81042a0ae0c796a21a9a877da
- affected>= 9cb837480424e78ed585376f944088246685aec3 and < 2912f3d40355dabc08fdbaaf2764d02445fe88dc
- affected>= 9cb837480424e78ed585376f944088246685aec3 and < 6f40246f4312fdbab5a13cc440adebf95eb2aa66
- affected>= 9cb837480424e78ed585376f944088246685aec3 and < 5a45d0aa1fa50a333ce5763ade744e2d89838667
- affected>= 9cb837480424e78ed585376f944088246685aec3 and < da3e44add94b05dfde56f898421922f5cf35705f
- affected>= 9cb837480424e78ed585376f944088246685aec3 and < 963af8d97a8c6a117134a8d0db1415e0489200b1
- affected5.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.