net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure
Summary
| CVE | CVE-2026-99212 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-28 11:17:42 UTC |
| Updated | 2026-10-31 13:17:59 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 7 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS: 0.001670000 probability, percentile 0.059320000 (date 2026-10-31)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 7 | HIGH | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | DECLARED | 7 | HIGH | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
HighPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea 664fd3205cbec71ac52c005ee705cd917bb6fb1a git | Not specified |
| CNA | Linux | Linux | affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea b8f141f65885810e24fc23b8a71692db62d535bf git | Not specified |
| CNA | Linux | Linux | affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea e677eda15df7d5ce256654343418043c7ffd6f9b git | Not specified |
| CNA | Linux | Linux | affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea 92143c5d80382588d5a3047a4f14023ee9ef6485 git | Not specified |
| CNA | Linux | Linux | affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea a7c7d0ff876377fea7ae876a28d6df8d9349df57 git | Not specified |
| CNA | Linux | Linux | affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea 91ece3efa064f0b3b3c67b9b045d9eeb4a034e43 git | Not specified |
| CNA | Linux | Linux | affected 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea 98d446b7c013254a8a7b49720557676a3a851fde git | Not specified |
| CNA | Linux | Linux | affected 2.6.30 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.30 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.224 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.191 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.161 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.115 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.59 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.13 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/e677eda15df7d5ce256654343418043c7ffd6f9b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/92143c5d80382588d5a3047a4f14023ee9ef6485 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/98d446b7c013254a8a7b49720557676a3a851fde | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a7c7d0ff876377fea7ae876a28d6df8d9349df57 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b8f141f65885810e24fc23b8a71692db62d535bf | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/91ece3efa064f0b3b3c67b9b045d9eeb4a034e43 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/664fd3205cbec71ac52c005ee705cd917bb6fb1a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.