Linux
net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < 664fd3205cbec71ac52c005ee705cd917bb6fb1a
- >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < b8f141f65885810e24fc23b8a71692db62d535bf
- >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < e677eda15df7d5ce256654343418043c7ffd6f9b
- >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < 92143c5d80382588d5a3047a4f14023ee9ef6485
- >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < a7c7d0ff876377fea7ae876a28d6df8d9349df57
- >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < 91ece3efa064f0b3b3c67b9b045d9eeb4a034e43
- >= 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea, < 98d446b7c013254a8a7b49720557676a3a851fde
Fixed in 664fd3205cbec71ac52c005ee705cd917bb6fb1a, b8f141f65885810e24fc23b8a71692db62d535bf, e677eda15df7d5ce256654343418043c7ffd6f9b, 92143c5d80382588d5a3047a4f14023ee9ef6485, a7c7d0ff876377fea7ae876a28d6df8d9349df57, 91ece3efa064f0b3b3c67b9b045d9eeb4a034e43, 98d446b7c013254a8a7b49720557676a3a851fde
- 2.6.30
Fixed in 0, 5.15.224, 6.1.191, 6.6.161, 6.12.115, 6.18.59, 7.2.13, 7.3
Mitigation
Upgrade Linux to 664fd3205cbec71ac52c005ee705cd917bb6fb1a or b8f141f65885810e24fc23b8a71692db62d535bf or e677eda15df7d5ce256654343418043c7ffd6f9b or 92143c5d80382588d5a3047a4f14023ee9ef6485 or a7c7d0ff876377fea7ae876a28d6df8d9349df57 or 91ece3efa064f0b3b3c67b9b045d9eeb4a034e43 or 98d446b7c013254a8a7b49720557676a3a851fde or later.
Upgrade Linux to 0 or 5.15.224 or 6.1.191 or 6.6.161 or 6.12.115 or 6.18.59 or 7.2.13 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.