IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d757c60eca9b22f4d108929a24401e0fdecda0b1 · < 4d809f69695d4e7d1378b3a072fa9aef23123018| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s IB/rdmavt code can call rvt_error_qp without holding the required r_lock. This can fail a lockdep assertion and may cause a race condition. The input does not specify how an attacker could trigger it or what access would be required.
Engineers running the Linux kernel should check whether their version includes the affected IB/rdmavt code; affected versions are not specified.