crypto: virtio - Add spinlock protection with virtqueue notification
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ fed93fb62e05c38152b0fc1dc9609639e63eed76 · < e69a7b0a71b6561b3b6459f1fded8d589f2e8ac2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: virtio - Add spinlock protection with virtqueue notification
When VM boots with one virtio-crypto PCI device and builtin backend, run openssl benchmark command with multiple processes, such as openssl speed -evp aes-128-cbc -engine afalg -seconds 10 -multi 32
openssl processes will hangup and there is error reported like this: virtio_crypto virtio0: dataq.0:id 3 is not a head!
It seems that the data virtqueue need protection when it is handled for virtio done notification. If the spinlock protection is added in virtcrypto_done_task(), openssl benchmark with multiple processes works well.
From the CVE record · Linux
The Linux kernel's virtio-crypto data virtqueue lacks spinlock protection during completion notification. In a VM with a virtio-crypto PCI device and built-in backend, multiple concurrent OpenSSL benchmark processes can hang. The input does not describe an attacker, authentication requirements, or user interaction.
Operators running Linux kernels with a virtio-crypto PCI device and built-in backend should check; affected versions are not specified.