[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122422-CVE-2022-50736-1cb3@gregkh>
Date: Wed, 24 Dec 2025 13:26:35 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50736: RDMA/siw: Fix immediate work request flush to completion queue
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
RDMA/siw: Fix immediate work request flush to completion queue
Correctly set send queue element opcode during immediate work request
flushing in post sendqueue operation, if the QP is in ERROR state.
An undefined ocode value results in out-of-bounds access to an array
for mapping the opcode between siw internal and RDMA core representation
in work completion generation. It resulted in a KASAN BUG report
of type 'global-out-of-bounds' during NFSoRDMA testing.
This patch further fixes a potential case of a malicious user which may
write undefined values for completion queue elements status or opcode,
if the CQ is memory mapped to user land. It avoids the same out-of-bounds
access to arrays for status and opcode mapping as described above.
The Linux kernel CVE team has assigned CVE-2022-50736 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.3 with commit 303ae1cdfdf7280ff4cfbbe65563b5ff15bb025b and fixed in 5.4.229 with commit 6af043089d3f1210776d19b6fdabea610d4c7699
Issue introduced in 5.3 with commit 303ae1cdfdf7280ff4cfbbe65563b5ff15bb025b and fixed in 5.10.163 with commit 75af03fdf35acf15a3977f7115f6b8d10dff4bc7
Issue introduced in 5.3 with commit 303ae1cdfdf7280ff4cfbbe65563b5ff15bb025b and fixed in 5.15.86 with commit f8d8fbd3b6d6cc3f25790cca5cffe8ded512fef6
Issue introduced in 5.3 with commit 303ae1cdfdf7280ff4cfbbe65563b5ff15bb025b and fixed in 6.0.16 with commit 355d2eca68c10d713a42f68e62044b3d1c300471
Issue introduced in 5.3 with commit 303ae1cdfdf7280ff4cfbbe65563b5ff15bb025b and fixed in 6.1.2 with commit f3d26a8589dfdeff328779b511f71fb90b10005e
Issue introduced in 5.3 with commit 303ae1cdfdf7280ff4cfbbe65563b5ff15bb025b and fixed in 6.2 with commit bdf1da5df9da680589a7f74448dd0a94dd3e1446
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-50736
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_cq.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/6af043089d3f1210776d19b6fdabea610d4c7699
https://git.kernel.org/stable/c/75af03fdf35acf15a3977f7115f6b8d10dff4bc7
https://git.kernel.org/stable/c/f8d8fbd3b6d6cc3f25790cca5cffe8ded512fef6
https://git.kernel.org/stable/c/355d2eca68c10d713a42f68e62044b3d1c300471
https://git.kernel.org/stable/c/f3d26a8589dfdeff328779b511f71fb90b10005e
https://git.kernel.org/stable/c/bdf1da5df9da680589a7f74448dd0a94dd3e1446
Powered by blists - more mailing lists