Linux kernel vulnerability enabling remote kernel memory corruption/RCE in RDMA subsystem; affects widely deployed OS kernels used across servers, cloud and HPC—high operational impact.
CVE-2026-97413
Integer underflow in Linux RDMA rtrs-srv enabling remote kernel memory corruption/RCE
Is CVE-2026-97413 being exploited?
Not confirmed. CVE-2026-97413 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.
How severe is CVE-2026-97413?
CVE-2026-97413 is rated Critical with a CVSS score of 9.8. 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-97413?
Yes. A fix has been recorded for CVE-2026-97413. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-97413 affect?
CVE-2026-97413 affects Linux kernel (RDMA/rtrs-srv enabled), Servers and appliances using RDMA, Cloud/HPC nodes with RDMA stacks. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-97413?
Install kernel update with rtrs-srv fix; restrict/untrusted RDMA access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote kernel memory corruption and likely remote code execution via crafted RDMA message (malicious usr_len causes out-of-bounds kernel access).
Immediate action required
- affected>= 9cb837480424e78ed585376f944088246685aec3 and < 24ad03bfeda05fca04c56677e57fd3d6bc3e9978
- affected>= 9cb837480424e78ed585376f944088246685aec3 and < c76e9123ab91a903396d26e6ab1b5caae5c6b149
- affected>= 9cb837480424e78ed585376f944088246685aec3 and < 54bf38b27afc08a0eb6b732f9c14eb8a4bcb66b5
- 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.