CVE-2022-49089
published 2025-02-26CVE-2022-49089: 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…
PriorityP415medium4.7CVSS 3.1
AVLACHPRLUINSUCNINAH
EPSS
0.19%
8.9th percentile
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.
Affected
20 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.17.3-1 (bookworm) | linux 5.17.3-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 5.0.4 < 5.1 | 5.1 |
| linux | linux | >= d757c60eca9b22f4d108929a24401e0fdecda0b1 < 8a50937227c385a477177c9ffa122b4230e40666 | 8a50937227c385a477177c9ffa122b4230e40666 |
| linux | linux | >= d757c60eca9b22f4d108929a24401e0fdecda0b1 < 43c2d7890ecabe527448a6c391fb2d9a5e6bbfe0 | 43c2d7890ecabe527448a6c391fb2d9a5e6bbfe0 |
| linux | linux | >= d757c60eca9b22f4d108929a24401e0fdecda0b1 < 92f1947c0d26060e978b3a9f21f32ce7c8c9cca3 | 92f1947c0d26060e978b3a9f21f32ce7c8c9cca3 |
| linux | linux | >= d757c60eca9b22f4d108929a24401e0fdecda0b1 < 77ffb2495a41098f9d6a14f8aefde3188da75944 | 77ffb2495a41098f9d6a14f8aefde3188da75944 |
| linux | linux | >= d757c60eca9b22f4d108929a24401e0fdecda0b1 < 57800cc36e55db0547461c49acf5cd84c0f502b0 | 57800cc36e55db0547461c49acf5cd84c0f502b0 |
| linux | linux | >= d757c60eca9b22f4d108929a24401e0fdecda0b1 < 4d809f69695d4e7d1378b3a072fa9aef23123018 | 4d809f69695d4e7d1378b3a072fa9aef23123018 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.113-1 | 5.10.113-1 |
| linux | linux_kernel | >= 0 < 5.17.3-1 | 5.17.3-1 |
| linux | linux_kernel | >= 0 < 5.17.3-1 | 5.17.3-1 |
| linux | linux_kernel | >= 0 < 5.17.3-1 | 5.17.3-1 |
| linux | linux_kernel | >= 5.0.4 < 5.4.189 | 5.4.189 |
| linux | linux_kernel | >= 5.11 < 5.15.34 | 5.15.34 |
| linux | linux_kernel | >= 5.16 < 5.16.20 | 5.16.20 |
| linux | linux_kernel | >= 5.17 < 5.17.3 | 5.17.3 |
| linux | linux_kernel | >= 5.5 < 5.10.111 | 5.10.111 |
CVSS provenance
nvdv3.14.7MEDIUMCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
osv4.7MEDIUM
vendor_debian4.7MEDIUM
vendor_redhat4.7MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition
vendor_redhat·2025-02-26·CVSS 4.7
CVE-2022-49089 [MEDIUM] kernel: IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition
kernel: IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition
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.
A flaw was found in the Linux kernel’s RDMA subsystem, which supports high-speed networking. Due to a missing safety check, two parts of the system could try to handle an err
Debian
CVE-2022-49089: linux - In the Linux kernel, the following vulnerability has been resolved: IB/rdmavt: ...
vendor_debian·2022·CVSS 4.7
CVE-2022-49089 [MEDIUM] CVE-2022-49089: linux - In the Linux kernel, the following vulnerability has been resolved: IB/rdmavt: ...
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.
Scope: local
bookworm: resolved (fixed in 5.17.3-1)
bullseye: resolved (fixed in 5.10.113-1)
forky: resolved (fixed in 5.17.3-1)
sid: resolved (fixed in 5.17.3-1)
trixie: resolved (fixed in 5.17.3-1)
GHSA
GHSA-jr72-7h43-2283: 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 docu
ghsa_unreviewed·2025-09-23
CVE-2022-49089 [MEDIUM] CWE-362 GHSA-jr72-7h43-2283: 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 docu
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.
OSV
CVE-2022-49089: 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 docume
osv·2025-02-26·CVSS 4.7
CVE-2022-49089 [MEDIUM] CVE-2022-49089: 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 docume
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.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/43c2d7890ecabe527448a6c391fb2d9a5e6bbfe0https://git.kernel.org/stable/c/4d809f69695d4e7d1378b3a072fa9aef23123018https://git.kernel.org/stable/c/57800cc36e55db0547461c49acf5cd84c0f502b0https://git.kernel.org/stable/c/77ffb2495a41098f9d6a14f8aefde3188da75944https://git.kernel.org/stable/c/8a50937227c385a477177c9ffa122b4230e40666https://git.kernel.org/stable/c/92f1947c0d26060e978b3a9f21f32ce7c8c9cca3
2025-02-26
Published