In the Linux kernel, the following vulnerability has been resolved: net/rds: don't let the rdma_cm…

Why it is Yellow

• CVSS 7.0 high
• On your watchlist: linux kernel

References

• https://git.kernel.org/stable/c/91ece3efa064f0b3b3c67b9b045d9eeb4a034e43
• https://git.kernel.org/stable/c/98d446b7c013254a8a7b49720557676a3a851fde
• https://git.kernel.org/stable/c/a7c7d0ff876377fea7ae876a28d6df8d9349df57
• https://git.kernel.org/stable/c/664fd3205cbec71ac52c005ee705cd917bb6fb1a
• https://git.kernel.org/stable/c/92143c5d80382588d5a3047a4f14023ee9ef6485
• https://git.kernel.org/stable/c/b8f141f65885810e24fc23b8a71692db62d535bf
• https://git.kernel.org/stable/c/e677eda15df7d5ce256654343418043c7ffd6f9b

Original 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.