CVE-2026-99212·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure rds_rdma_cm_event_handler_cmn() hands the return value of rdma_resolve_route() straight back to the rdma_cm on RDMA_CM_EVENT_ADDR_RESOLVED. A synchronous failure there - -ENOMEM from the route work allocation, an SA query that cannot be set up, a RoCE route with no usable device - makes addr_handler() destroy the id the event was delivered on. That id is ic->i_cm_id, and nothing clears the pointer: the connection sits in RDS_CONN_CONNECTING with a freed id until its shutdown calls rdma_disconnect() and rdma_destroy_id() on it. The ROUTE_RESOLVED case already avoids this: rds_ib_cm_initiate_connect() forces a zero return while ic->i_cm_id == cm_id, as the comment there explains. Do the same here - drop the connection and return 0 - so the id stays RDS's to destroy from the shutdown, and the reconnect gets a fresh one.
- Severity
- high
- Software
- Kernel
- Fixed in
- 5.15.224, 6.1.191, 6.6.161, 6.12.115, 6.18.59, 7.2.13, 7.3
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.16% — higher than 5% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-99212 scores 7 on CVSS, so a successful attack would be serious — but at 0.16%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
How to fix this CVE
Update your Linux kernel to a patched stable release to resolve a resource management flaw in the RDS/RDMA subsystem. Choose the fixed version matching your current kernel branch: 5.15.224, 6.1.191, 6.6.161, 6.12.115, 6.18.59, or 7.2.13. Most users should obtain the patched kernel through their distribution's package manager rather than upgrading to a different major version.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your current kernel version with `uname -r` and compare it against the fixed versions for your branch (5.15.224+, 6.1.191+, 6.6.161+, 6.12.115+, 6.18.59+, or 7.2.13+).
- Step 2: Verify if RDS/RDMA is in use by checking `lsmod | grep rds` and `lsmod | grep rdma`; if empty, this subsystem is not actively loaded.
- Step 3: Search kernel logs for RDMA connection failures using `sudo journalctl -b | grep -i 'rds\|rdma\|addr_resolved'` to identify systems under load.
- Step 4: After patching, reboot the system and confirm the new kernel version with `uname -r`, then verify RDS modules load cleanly with `sudo modprobe rds` and `sudo modprobe rds_rdma`.
FAQ
What is CVE-2026-99212?
This vulnerability affects the Linux kernel's RDS/RDMA networking subsystem, where a resource management error allows the RDMA connection manager to destroy a connection identifier that the RDS module still owns, leaving a freed pointer in memory until shutdown and causing potential crashes or undefined behavior.
Is CVE-2026-99212 being actively exploited?
No, this CVE is not listed on the CISA Known Exploited Vulnerabilities catalog and no public exploits are available.
What versions of Kernel are affected by CVE-2026-99212?
All kernel versions prior to the fixed releases in each stable branch are affected: Linux 5.15.x before 5.15.224, 6.1.x before 6.1.191, 6.6.x before 6.6.161, 6.12.x before 6.12.115, 6.18.x before 6.18.59, 7.2.x before 7.2.13, and mainline before 7.3.
How do I check if my server is vulnerable to CVE-2026-99212?
Run `uname -r` to get your kernel version, then compare it against the fixed versions for your branch. If your version is older than the corresponding fix and you use RDS/RDMA (check via `lsmod | grep -E 'rds|rdma'`), your system is vulnerable.
Does Defensia detect CVE-2026-99212?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-99212 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/664fd3205cbec71ac52c005ee705cd917bb6fb1a
- https://git.kernel.org/stable/c/91ece3efa064f0b3b3c67b9b045d9eeb4a034e43
- https://git.kernel.org/stable/c/92143c5d80382588d5a3047a4f14023ee9ef6485
- https://git.kernel.org/stable/c/98d446b7c013254a8a7b49720557676a3a851fde
- https://git.kernel.org/stable/c/a7c7d0ff876377fea7ae876a28d6df8d9349df57
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-99212. Free for 1 server.
Get started free