linux-cve-announce - CVE-2023-54201: RDMA/efa: Fix wrong resources deallocation order

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025123030-CVE-2023-54201-3f26@gregkh>
Date: Tue, 30 Dec 2025 13:10:09 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54201: RDMA/efa: Fix wrong resources deallocation order

From: Greg Kroah-Hartman <gregkh@...nel.org>

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.

The Linux kernel CVE team has assigned CVE-2023-54201 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.7 with commit ff6629f88c529b07d9704c656c64dae76910e3e9 and fixed in 6.1.53 with commit cf38960386f3cc4abf395e556af915e4babcafd2
	Issue introduced in 5.7 with commit ff6629f88c529b07d9704c656c64dae76910e3e9 and fixed in 6.4.16 with commit e79db2f51a564fd4daa3e508b987df5e81c34b20
	Issue introduced in 5.7 with commit ff6629f88c529b07d9704c656c64dae76910e3e9 and fixed in 6.5.3 with commit 24f9884971f9b34915b67baacf7350a3f6f19ea4
	Issue introduced in 5.7 with commit ff6629f88c529b07d9704c656c64dae76910e3e9 and fixed in 6.6 with commit dc202c57e9a1423aed528e4b8dc949509cd32191

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-54201
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/infiniband/hw/efa/efa_verbs.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/cf38960386f3cc4abf395e556af915e4babcafd2
	https://git.kernel.org/stable/c/e79db2f51a564fd4daa3e508b987df5e81c34b20
	https://git.kernel.org/stable/c/24f9884971f9b34915b67baacf7350a3f6f19ea4
	https://git.kernel.org/stable/c/dc202c57e9a1423aed528e4b8dc949509cd32191