CVE-2026-99212: Linux Vulnerability (CVSS 7)

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.

Metrics

CVSS 3.1

7/10

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability

0.16%

5.2th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < 664fd3205cbec71ac52c005ee705cd917bb6fb1a; >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < b8f141f65885810e24fc23b8a71692db62d535bf; >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < e677eda15df7d5ce256654343418043c7ffd6f9b; >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < 92143c5d80382588d5a3047a4f14023ee9ef6485; >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < a7c7d0ff876377fea7ae876a28d6df8d9349df57; >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < 91ece3efa064f0b3b3c67b9b045d9eeb4a034e43; >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < 98d446b7c013254a8a7b49720557676a3a851fde
Linux	Linux	2.6.30

References

Timeline

Published: Oct 28, 2026
Last Modified: Oct 31, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-99212?

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.

How severe is CVE-2026-99212?

CVE-2026-99212 has a CVSS score of 7/10 (HIGH severity). The EPSS model estimates a 0.16% probability of exploitation in the next 30 days.

How do I fix CVE-2026-99212?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →