CVE-2026-99212: Linux

High severity, CVSS 7.0. EPSS: 0.1% probability of exploitation activity in the next 30 days.

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.

What to do

The record states a fixed version for each range of affected versions. Update to the one for the range your version is in: a later release on another branch may not have the fix.

  • Linux, from 2.6.30, before 5.15.224: fixed in 5.15.224
  • Linux, from 5.16, before 6.1.191: fixed in 6.1.191
  • Linux, from 6.2, before 6.6.161: fixed in 6.6.161
  • Linux, from 6.7, before 6.12.115: fixed in 6.12.115
  • Linux, from 6.13, before 6.18.59: fixed in 6.18.59
  • Linux, from 6.19, before 7.2.13: fixed in 7.2.13

Affected products

  • Linux Linux: from 2.6.30, before 5.15.224 (fixed in 5.15.224); from 5.16, before 6.1.191 (fixed in 6.1.191); from 6.2, before 6.6.161 (fixed in 6.6.161); from 6.7, before 6.12.115 (fixed in 6.12.115); from 6.13, before 6.18.59 (fixed in 6.18.59); from 6.19, before 7.2.13 (fixed in 7.2.13)

Published 2026-10-28. Last modified 2026-10-31.