bus: mhi: host: Drop chan lock before queuing buffers
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1d3173a3bae7039b765a0956e3e4bf846dbaacb8 · < 01bd694ac2f682fb8017e16148b928482bc8fa4b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bus: mhi: host: Drop chan lock before queuing buffers
Ensure read and write locks for the channel are not taken in succession by dropping the read lock from parse_xfer_event() such that a callback given to client can potentially queue buffers and acquire the write lock in that process. Any queueing of buffers should be done without channel read lock acquired as it can result in multiple locks and a soft lockup.
[mani: added fixes tag and cc'ed stable]
From the CVE record · Linux
The Linux kernel’s MHI host code can hold a channel read lock while invoking a client callback. If that callback queues buffers and acquires the channel write lock, the resulting lock contention can cause a soft lockup. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with MHI host support should check their kernel versions against the vendor advisory; affected versions are not specified in the input.