Sasha Levin
2020-Jun-05 14:10 UTC
[PATCH v3 2/3] crypto: virtio: Fix use-after-free in virtio_crypto_skcipher_finalize_req()
<20200123101000.GB24255 at Red>
References: <20200602070501.2023-3-longpeng2 at huawei.com>
<20200123101000.GB24255 at Red>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: dbaf0624ffa5 ("crypto: add virtio-crypto driver").
The bot has tested the following trees: v5.6.15, v5.4.43, v4.19.125, v4.14.182.
v5.6.15: Build OK!
v5.4.43: Failed to apply! Possible dependencies:
eee1d6fca0a0 ("crypto: virtio - switch to skcipher API")
v4.19.125: Failed to apply! Possible dependencies:
eee1d6fca0a0 ("crypto: virtio - switch to skcipher API")
v4.14.182: Failed to apply! Possible dependencies:
500e6807ce93 ("crypto: virtio - implement missing support for output
IVs")
67189375bb3a ("crypto: virtio - convert to new crypto engine API")
d0d859bb87ac ("crypto: virtio - Register an algo only if it's
supported")
e02b8b43f55a ("crypto: virtio - pr_err() strings should end with
newlines")
eee1d6fca0a0 ("crypto: virtio - switch to skcipher API")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha