{"apiVersion":"1.0","identifier":"CVE-2026-99212","description":"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.","publishedAt":"2026-10-28T11:17:42","lastModifiedAt":"2026-10-31T13:17:59","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-99212","cvssScore":7,"cvssVector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","epssProbability":0.00118,"riskScore":0.71,"affectedProduct":"Linux kernel","affectedVersions":"unknown","vulnerabilityType":"Kernel","operatingSystems":[],"links":{"self":"https://www.redsauce.net/api/cves/CVE-2026-99212","webPages":{"es":"https://www.redsauce.net/es/cves/CVE-2026-99212","en":"https://www.redsauce.net/en/cves/CVE-2026-99212","fr":"https://www.redsauce.net/fr/cves/CVE-2026-99212","pt":"https://www.redsauce.net/pt/cves/CVE-2026-99212","de":"https://www.redsauce.net/de/cves/CVE-2026-99212","sk":"https://www.redsauce.net/sk/cves/CVE-2026-99212","el":"https://www.redsauce.net/el/cves/CVE-2026-99212"},"source":"https://nvd.nist.gov/vuln/detail/CVE-2026-99212"}}