CVE-2026-97413
Linux kernel vulnerability
- Published24 Sept 2026
Description
In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Fix integer underflow in process_read and process_write usr_len is read from a network-supplied message field (le16_to_cpu) and used to compute data_len = off - usr_len without validating that usr_len <= off. A malicious RDMA client can send usr_len > off causing an integer underflow, resulting in data_len wrapping to a huge size_t value which is then passed to the rdma_ev callback as a memory length, leading to out-of-bounds memory access. Fix by reading and validating usr_len <= off before rtrs_srv_get_ops_ids() in both process_read() and process_write(), ensuring the early return path acquires no reference and has no resource leak.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/24ad03bfeda05fca04c56677e57fd3d6bc3e9978
- https://git.kernel.org/stable/c/2c52b2afded988233cd4ccc185cf5147bbc77a76
- https://git.kernel.org/stable/c/54bf38b27afc08a0eb6b732f9c14eb8a4bcb66b5
- https://git.kernel.org/stable/c/6b1e26e70d7ca9f0906af2283558a530eeb1f066
- https://git.kernel.org/stable/c/b042b4947752df0b3d16e683ac09fb4f7f0e33e0
- https://git.kernel.org/stable/c/c76e9123ab91a903396d26e6ab1b5caae5c6b149
Frequently asked
Is CVE-2026-97413 being actively exploited?
CVE-2026-97413 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.50%.
How severe is CVE-2026-97413?
CVE-2026-97413 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.50% probability of exploitation.
How do I fix CVE-2026-97413?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-97413 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.