CVE-2026-99212

net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure

  • High 7.0

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.

Key facts

Published
28 Oct 2026
Last changed
31 Oct 2026
Assigned by
Linux
EPSS
0.118% likely to be exploited in the next 30 days, higher than 1.744% of CVEs (scores for 16 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.0CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea up to but excluding 664fd3205cbec71ac52c005ee705cd917bb6fb1a (affected)
  • 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea up to but excluding b8f141f65885810e24fc23b8a71692db62d535bf (affected)
  • 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea up to but excluding e677eda15df7d5ce256654343418043c7ffd6f9b (affected)
  • 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea up to but excluding 92143c5d80382588d5a3047a4f14023ee9ef6485 (affected)
  • 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea up to but excluding a7c7d0ff876377fea7ae876a28d6df8d9349df57 (affected)
  • 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea up to but excluding 91ece3efa064f0b3b3c67b9b045d9eeb4a034e43 (affected)
  • 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea up to but excluding 98d446b7c013254a8a7b49720557676a3a851fde (affected)
LinuxLinux
  • Default status: affected
  • 2.6.30 (affected)
  • 0 up to but excluding 2.6.30 (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.161 up to and including 6.6.* (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.59 up to and including 6.18.* (unaffected)
  • 7.2.13 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 28 Oct 2026 Published

References