svcrdma: Reorder rpcrdma_rn_unregister before rdma_destroy_id

Summary

In the Linux kernel, the following vulnerability has been resolved: svcrdma: Reorder rpcrdma_rn_unregister before rdma_destroy_id svc_rdma_free() caches rdma->sc_cm_id->device before teardown, then calls rdma_destroy_id(sc_cm_id) which frees the cm_id. rpcrdma_rn_unregister() follows, but between those two calls the transport's sc_rn entry is still installed in the device's rd_xa. A concurrent ib_unregister_device walk can dispatch svc_rdma_xprt_done() against the now-freed sc_cm_id. Move rpcrdma_rn_unregister() before rdma_destroy_id() so the transport's notification entry is removed from the xarray before the cm_id it references is destroyed. Also guard the sc_cm_id dereference with a NULL check: the following patches introduce paths that reach svc_rdma_free() with sc_cm_id == NULL (listener create failure, ADDR_CHANGE replacement failure).

Timeline

1. Sep 11, 2026, 7:44 PM UTCCVE published
2. Oct 19, 2026, 8:48 AM UTCRecord last updated

Affected versions

• Linux Linux

  From c4de97f7c45434985e5dbf2d6ccc9eca676e37fe · fixed in fcd4a752ac840d39356f4d2a424d3aca4e39716b; From c4de97f7c45434985e5dbf2d6ccc9eca676e37fe · fixed in 9f2f5d0999364c7070306cd422d8babc2621070d; From c4de97f7c45434985e5dbf2d6ccc9eca676e37fe · fixed in cfca6eb3345ba4a23cf9a1153ad09bf19faabfc9; From c4de97f7c45434985e5dbf2d6ccc9eca676e37fe · fixed in 4488e912973773d64368828acf3b8e39d93650ae

• Linux Linux

  6.12

• KernelLinux

  From 6.12.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.4

References 4