| 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
| ||
|
Message-ID: <2025022658-CVE-2022-49089-2a32@gregkh> Date: Wed, 26 Feb 2025 02:54:54 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2022-49089: IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition Description =========== In the Linux kernel, the following vulnerability has been resolved: IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition The documentation of the function rvt_error_qp says both r_lock and s_lock need to be held when calling that function. It also asserts using lockdep that both of those locks are held. However, the commit I referenced in Fixes accidentally makes the call to rvt_error_qp in rvt_ruc_loopback no longer covered by r_lock. This results in the lockdep assertion failing and also possibly in a race condition. The Linux kernel CVE team has assigned CVE-2022-49089 to this issue. Affected and fixed versions =========================== Issue introduced in 5.1 with commit d757c60eca9b22f4d108929a24401e0fdecda0b1 and fixed in 5.4.189 with commit 8a50937227c385a477177c9ffa122b4230e40666 Issue introduced in 5.1 with commit d757c60eca9b22f4d108929a24401e0fdecda0b1 and fixed in 5.10.111 with commit 43c2d7890ecabe527448a6c391fb2d9a5e6bbfe0 Issue introduced in 5.1 with commit d757c60eca9b22f4d108929a24401e0fdecda0b1 and fixed in 5.15.34 with commit 92f1947c0d26060e978b3a9f21f32ce7c8c9cca3 Issue introduced in 5.1 with commit d757c60eca9b22f4d108929a24401e0fdecda0b1 and fixed in 5.16.20 with commit 77ffb2495a41098f9d6a14f8aefde3188da75944 Issue introduced in 5.1 with commit d757c60eca9b22f4d108929a24401e0fdecda0b1 and fixed in 5.17.3 with commit 57800cc36e55db0547461c49acf5cd84c0f502b0 Issue introduced in 5.1 with commit d757c60eca9b22f4d108929a24401e0fdecda0b1 and fixed in 5.18 with commit 4d809f69695d4e7d1378b3a072fa9aef23123018 Issue introduced in 5.0.4 with commit 25636de95557a95d54ac30be94af3748345a0a90 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-49089 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/rdmavt/qp.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/8a50937227c385a477177c9ffa122b4230e40666 https://git.kernel.org/stable/c/43c2d7890ecabe527448a6c391fb2d9a5e6bbfe0 https://git.kernel.org/stable/c/92f1947c0d26060e978b3a9f21f32ce7c8c9cca3 https://git.kernel.org/stable/c/77ffb2495a41098f9d6a14f8aefde3188da75944 https://git.kernel.org/stable/c/57800cc36e55db0547461c49acf5cd84c0f502b0 https://git.kernel.org/stable/c/4d809f69695d4e7d1378b3a072fa9aef23123018
Powered by blists - more mailing lists