RDMA/core: Fix potential use after free in counter_release()

Summary

In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix potential use after free in counter_release() When accessing a counter via the netlink path the only synchronization mechanism for the said counter is rdma_restrack_get(). Currently, rdma_restrack_del() is invoked at the end of counter_release(), which is too late, since by that point vendor-specific resources associated with the counter might already be freed. This can leave a short window where the counter remains accessible through restrack, leading to a potential use-after-free. Fix this by moving the rdma_restrack_del() call to be before the freeing of the vendor-specific resources, ensuring that the counter is removed from restrack before its internal resources are released. This guarantees that no new users hold references to a counter that is in the process of destruction.

Timeline

1. Sep 17, 2026, 4:10 PM UTCCVE published
2. Oct 19, 2026, 9:04 AM UTCRecord last updated

Affected versions

• Linux Linux

  From 99fa331dc8629be55ac7a0cca0dc56492070ddac · fixed in 5eb0c57a8b568eb08f464861d84d518a2af939ac; From 99fa331dc8629be55ac7a0cca0dc56492070ddac · fixed in d5cc211e8c39e46f357d30a092d683e84d560de9; From 99fa331dc8629be55ac7a0cca0dc56492070ddac · fixed in 2f0c6705e26ba92c0c6b0b0908a2d3f35a039d5b; From 99fa331dc8629be55ac7a0cca0dc56492070ddac · fixed in 8c013e3a8d8273da4d47bf1c27f016a3551996f5; From 99fa331dc8629be55ac7a0cca0dc56492070ddac · fixed in 64c72390d8407ea86de712a477c796b07d37abc4; From 99fa331dc8629be55ac7a0cca0dc56492070ddac · fixed in 235ef2d0e750885c29340b0fc40620a7a4f52e12

• Linux Linux

  5.3

• KernelLinux

  From 5.3.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6

References 6