Linux Kernel up to 5.17.2 rvt_error_qp race condition

Summaryinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 5.4.188/5.10.110/5.15.33/5.16.19/5.17.2. The impacted element is the function rvt_error_qp. The manipulation results in race condition. This vulnerability was named CVE-2022-49089. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 5.4.188/5.10.110/5.15.33/5.16.19/5.17.2. It has been classified as problematic. Affected is the function rvt_error_qp. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. The impact remains unknown. CVE summarizes:

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 advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2022-49089 since 02/26/2025. The exploitability is told to be difficult. There are known technical details, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 232643 (SUSE SLES12 Security Update : kernel (SUSE-SU-2025:0834-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.4.189, 5.10.111, 5.15.34, 5.16.20 or 5.17.3 eliminates this vulnerability. Applying the patch 8a50937227c385a477177c9ffa122b4230e40666/43c2d7890ecabe527448a6c391fb2d9a5e6bbfe0/92f1947c0d26060e978b3a9f21f32ce7c8c9cca3/77ffb2495a41098f9d6a14f8aefde3188da75944/57800cc36e55db0547461c49acf5cd84c0f502b0/4d809f69695d4e7d1378b3a072fa9aef23123018 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (232643). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.4.188
• 5.10.110
• 5.15.0
• 5.15.1
• 5.15.2
• 5.15.3
• 5.15.4
• 5.15.5
• 5.15.6
• 5.15.7
• 5.15.8
• 5.15.9
• 5.15.10
• 5.15.11
• 5.15.12
• 5.15.13
• 5.15.14
• 5.15.15
• 5.15.16
• 5.15.17
• 5.15.18
• 5.15.19
• 5.15.20
• 5.15.21
• 5.15.22
• 5.15.23
• 5.15.24
• 5.15.25
• 5.15.26
• 5.15.27
• 5.15.28
• 5.15.29
• 5.15.30
• 5.15.31
• 5.15.32
• 5.15.33
• 5.16.0
• 5.16.1
• 5.16.2
• 5.16.3
• 5.16.4
• 5.16.5
• 5.16.6
• 5.16.7
• 5.16.8
• 5.16.9
• 5.16.10
• 5.16.11
• 5.16.12
• 5.16.13
• 5.16.14
• 5.16.15
• 5.16.16
• 5.16.17
• 5.16.18
• 5.16.19
• 5.17.0
• 5.17.1
• 5.17.2

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion