---
id: CVE-2026-99212
title: 'net/rds: don''t let the rdma_cm destroy an id RDS still owns on route failure'
summary: |-
  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 ba…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea <
    a7c7d0ff876377fea7ae876a28d6df8d9349df57
  - >-
    Linux >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea <
    91ece3efa064f0b3b3c67b9b045d9eeb4a034e43
  - >-
    Linux >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea <
    98d446b7c013254a8a7b49720557676a3a851fde
  - Linux 2.6.30
published: '2026-10-28'
updated: '2026-10-28'
sourceUpdated: '2026-10-28T10:36:05.612Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-99212'
references:
  - url: 'https://git.kernel.org/stable/c/a7c7d0ff876377fea7ae876a28d6df8d9349df57'
  - url: 'https://git.kernel.org/stable/c/91ece3efa064f0b3b3c67b9b045d9eeb4a034e43'
  - url: 'https://git.kernel.org/stable/c/98d446b7c013254a8a7b49720557676a3a851fde'
tags:
  - cve.org
ingestedAt: '2026-10-28T11:09:40.354Z'
---

## Overview

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.

## Affected

- `Linux >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea < a7c7d0ff876377fea7ae876a28d6df8d9349df57`
- `Linux >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea < 91ece3efa064f0b3b3c67b9b045d9eeb4a034e43`
- `Linux >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea < 98d446b7c013254a8a7b49720557676a3a851fde`
- `Linux 2.6.30`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.