crypto: api - Use work queue in crypto_destroy_instance
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 · < 9ae4577bc077a7e32c3c7d442c95bc76865c0f17| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: api - Use work queue in crypto_destroy_instance
The function crypto_drop_spawn expects to be called in process context. However, when an instance is unregistered while it still has active users, the last user may cause the instance to be freed in atomic context.
Fix this by delaying the freeing to a work queue.
From the CVE record · Linux
The Linux kernel crypto API can free an instance in atomic context, even though crypto_drop_spawn expects process context. This can happen when an instance is unregistered while it still has active users and the last user releases it; the input does not describe an attacker path or exploitation conditions.
Engineers running the Linux kernel should check their vendor's advisory for affected versions, which are not specified here.