In the Linux kernel, the following vulnerability has been resolved: crypto: essiv - Handle EBUSY correctly As it is essiv only handles the special return value of EINPROGERSS, which means that in all other cases it will free data related to the request. However, as the caller of essiv may specify MAY_BACKLOG, we also need to expect EBUSY and treat it in the same way. Otherwise backlogged requests will trigger a use-after-free.
https://git.kernel.org/stable/c/c61e7d182ee3f3f5ecf18a2964e303d49c539b52
https://git.kernel.org/stable/c/b5a772adf45a32c68bef28e60621f12617161556
https://git.kernel.org/stable/c/a006aa3eedb8bfd6fe317c3cfe9c86ffe76b2385
https://git.kernel.org/stable/c/840a1d3b77c1b062bd62b4733969a5b1efc274ce
https://git.kernel.org/stable/c/796e02cca30a67322161f0745e5ce994bbe75605
https://git.kernel.org/stable/c/69c67d451fc19d88e54f7d97e8e7c093e08357e1