Live › vulnerability › CVE-2026-99212
Go to dashboardWhen RDS route resolution fails synchronously on the RDMA address-resolved event, the rdma_cm layer destroys the connection's cm id while RDS still holds the pointer. The connection then operates on a freed id until shutdown, which is a use-after-free that can crash the kernel.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 11:32 UTC. All times on this page are UTC.
Systems running a Linux kernel with the RDS socket protocol and RDMA connection manager in use, typically RDS over InfiniBand or RoCE. Hosts that do not load the rds module or use RDS can skip it.
No product ranges from the sources yet.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-99212")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.