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.
Published: 2026-09-24
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Use after free potentially leading to memory corruption or arbitrary code execution
Action: Apply patch
AI Analysis

Impact

The vulnerability is a use‑after‑free within the RDMA core code, specifically in the process that frees DMA hash table entries (dmah). When the RDMA context is released via the netlink interface, the code releases vendor‑specific resources before correctly removing the dmah from the restriction tracking list. This creates a short window where the dmah can still be referenced, allowing a use‑after‑free scenario that could corrupt memory or enable arbitrary code execution. Additionally, this flaw aligns with CWE‑825: Defect in Resource Management, due to the improper sequencing of cleanup steps.

Affected Systems

The affected product is the Linux kernel, particularly the RDMA core subsystem. The vendors are listed as Linux:Linux. No specific kernel version range is provided in the advisory, but any kernel version containing the buggy dmah cleanup logic before the fix commit would be vulnerable.

Risk and Exploitability

The CVSS score is 5.5, and the EPSS score is < 1%, indicating the vulnerability has a medium severity and a very low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. Exploitation would likely require a local privileged attacker who can interact with the RDMAue abstraction over netlink, and precise timing to trigger the use‑after‑free before the removed dmah is garbage‑collected. Given the lack of public exploits and the need for local access, the overall risk can be considered moderate to low, but the potential impact warrants immediate remediation.

Generated by OpenCVE AI on October 1, 2026 at 22:17 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the kernel to a version that includes the commit fixing the dmah deletion ordering
  • Reboot the system so that the updated kernel is in use
  • If RDMA functionality is not required on the host, disable the RDMA subsystem to reduce attack surface

Generated by OpenCVE AI on October 1, 2026 at 22:17 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 01 Oct 2026 20:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416

Tue, 29 Sep 2026 13:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-825
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Fri, 25 Sep 2026 08:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416

Thu, 24 Sep 2026 16:00:00 +0000

Type Values Removed Values Added
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.
Title RDMA/core: Fix potential use after free in uverbs_free_dmah()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-19T09:08:20.283Z

Reserved: 2026-09-17T16:02:15.097Z

Link: CVE-2026-93267

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-24T16:17:23.570

Modified: 2026-10-19T10:17:18.093

Link: CVE-2026-93267

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-24T00:00:00Z

Links: CVE-2026-93267 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-01T22:30:14Z

Weaknesses
  • CWE-825

    Expired Pointer Dereference