VYPR
Unrated severityNVD Advisory· Published Dec 30, 2025· Updated Apr 15, 2026

CVE-2023-54201

CVE-2023-54201

Description

In the Linux kernel, the following vulnerability has been resolved:

RDMA/efa: Fix wrong resources deallocation order

When trying to destroy QP or CQ, we first decrease the refcount and potentially free memory regions allocated for the object and then request the device to destroy the object. If the device fails, the object isn't fully destroyed so the user/IB core can try to destroy the object again which will lead to underflow when trying to decrease an already zeroed refcount.

Deallocate resources in reverse order of allocating them to safely free them.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

In the Linux kernel's RDMA/efa driver, a wrong resource deallocation order in QP/CQ destruction can cause a refcount underflow and use-after-free.

Vulnerability

CVE-2023-54201 is a bug in the Linux kernel's RDMA/efa driver related to improper resource deallocation order when destroying Queue Pairs (QP) or Completion Queues (CQ). The driver first decreases the reference count and potentially frees memory regions allocated for the object, and only then requests the device to destroy the object. If the device fails to destroy the object, the object remains partially alive, but the refcount has already been decremented to zero. A subsequent attempt to destroy the same object will decrement an already zeroed refcount, leading to an underflow and potential use-after-free [1][2].

Exploitation

An attacker with local access and the ability to trigger QP or CQ destruction (e.g., via ibv_destroy_qp or ibv_destroy_cq) could exploit this race condition. The vulnerability does not require special privileges beyond those needed to use RDMA resources. The attack surface is limited to systems using the EFA (Elastic Fabric Adapter) driver, which is primarily used in AWS instances for high-performance computing [1][2].

Impact

Successful exploitation could lead to a use-after-free condition, which could lead to memory corruption, denial of service, or potentially privilege escalation. The exact impact depends on the system configuration and the attacker's ability to control the freed memory [1][2].

Mitigation

The fix is to deallocate resources in reverse order of allocation, ensuring that the refcount is only decremented after the device has successfully destroyed the object. The patch has been applied to the Linux kernel stable branches [1][2]. Users should update their kernel to a version containing the fix.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

4

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

4

News mentions

0

No linked articles in our index yet.