CVE-2026-99212
net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure
- Published
- Updated
- Reserved
- Assigned by
- Linux
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (6 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.
Affected products
- affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea – < 664fd3205cbec71ac52c005ee705cd917bb6fb1a
- affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea – < b8f141f65885810e24fc23b8a71692db62d535bf
- affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea – < e677eda15df7d5ce256654343418043c7ffd6f9b
- affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea – < 92143c5d80382588d5a3047a4f14023ee9ef6485
- affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea – < a7c7d0ff876377fea7ae876a28d6df8d9349df57
- affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea – < 91ece3efa064f0b3b3c67b9b045d9eeb4a034e43
- affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea – < 98d446b7c013254a8a7b49720557676a3a851fde
- affected 2.6.30
- unaffected < 2.6.30
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.161 – ≤ 6.6.*
- unaffected 6.12.115 – ≤ 6.12.*
- unaffected 6.18.59 – ≤ 6.18.*
- unaffected 7.2.13 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References (7)
- https://git.kernel.org/stable/c/664fd3205cbec71ac52c005ee705cd917bb6fb1a (opens in a new tab)
- https://git.kernel.org/stable/c/b8f141f65885810e24fc23b8a71692db62d535bf (opens in a new tab)
- https://git.kernel.org/stable/c/e677eda15df7d5ce256654343418043c7ffd6f9b (opens in a new tab)
- https://git.kernel.org/stable/c/92143c5d80382588d5a3047a4f14023ee9ef6485 (opens in a new tab)
- https://git.kernel.org/stable/c/a7c7d0ff876377fea7ae876a28d6df8d9349df57 (opens in a new tab)
- https://git.kernel.org/stable/c/91ece3efa064f0b3b3c67b9b045d9eeb4a034e43 (opens in a new tab)
- https://git.kernel.org/stable/c/98d446b7c013254a8a7b49720557676a3a851fde (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2026-99212)Record last updated .