linux-cve-announce - CVE-2022-50666: RDMA/siw: Fix QP destroy to wait for all references dropped.

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: <2025120944-CVE-2022-50666-0d75@gregkh>
Date: Tue,  9 Dec 2025 10:30:51 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50666: RDMA/siw: Fix QP destroy to wait for all references dropped.

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

Description
===========

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

RDMA/siw: Fix QP destroy to wait for all references dropped.

Delay QP destroy completion until all siw references to QP are
dropped. The calling RDMA core will free QP structure after
successful return from siw_qp_destroy() call, so siw must not
hold any remaining reference to the QP upon return.
A use-after-free was encountered in xfstest generic/460, while
testing NFSoRDMA. Here, after a TCP connection drop by peer,
the triggered siw_cm_work_handler got delayed until after
QP destroy call, referencing a QP which has already freed.

The Linux kernel CVE team has assigned CVE-2022-50666 to this issue.

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

	Issue introduced in 5.3 with commit 303ae1cdfdf7280ff4cfbbe65563b5ff15bb025b and fixed in 5.15.75 with commit 5c75d608fad58301b63e7d69200c13c3a1d411da
	Issue introduced in 5.3 with commit 303ae1cdfdf7280ff4cfbbe65563b5ff15bb025b and fixed in 5.19.17 with commit 74ad141e995a730760b1bcfa14854b7f1057d6bc
	Issue introduced in 5.3 with commit 303ae1cdfdf7280ff4cfbbe65563b5ff15bb025b and fixed in 6.0.3 with commit 0ed8bf9d0bb19f3f5eedd73f04aaf5bba9ac0737
	Issue introduced in 5.3 with commit 303ae1cdfdf7280ff4cfbbe65563b5ff15bb025b and fixed in 6.1 with commit a3c278807a459e6f50afee6971cabe74cccfb490

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-2022-50666
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/sw/siw/siw.h
	drivers/infiniband/sw/siw/siw_qp.c
	drivers/infiniband/sw/siw/siw_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/5c75d608fad58301b63e7d69200c13c3a1d411da
	https://git.kernel.org/stable/c/74ad141e995a730760b1bcfa14854b7f1057d6bc
	https://git.kernel.org/stable/c/0ed8bf9d0bb19f3f5eedd73f04aaf5bba9ac0737
	https://git.kernel.org/stable/c/a3c278807a459e6f50afee6971cabe74cccfb490