firmware: qcom: scm: Mark get_wq_ctx() as atomic call
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.6.496.10.86.11In the Linux kernel, the following vulnerability has been resolved:
firmware: qcom: scm: Mark get_wq_ctx() as atomic call
Currently get_wq_ctx() is wrongly configured as a standard call. When two SMC calls are in sleep and one SMC wakes up, it calls get_wq_ctx() to resume the corresponding sleeping thread. But if get_wq_ctx() is interrupted, goes to sleep and another SMC call is waiting to be allocated a waitq context, it leads to a deadlock.
To avoid this get_wq_ctx() must be an atomic call and can't be a standard SMC call. Hence mark get_wq_ctx() as a fast call.
From the CVE record · Linux
The Linux kernel configures get_wq_ctx() in Qualcomm SCM as a standard call rather than an atomic fast call. Under the described combination of sleeping, interrupted, and waiting SMC calls, this can cause a deadlock. The input does not specify an attacker or any access or interaction requirements.
Engineers running Linux kernels with Qualcomm SCM should check whether their kernel includes the fix; affected versions are not specified.