Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
be1eb7f78aa8fbe34779c56c266ccd0364604e71 to < c61e7d182ee3f3f5ecf18a2964e303d49c539b52affectedbe1eb7f78aa8fbe34779c56c266ccd0364604e71 to < 796e02cca30a67322161f0745e5ce994bbe75605affectedbe1eb7f78aa8fbe34779c56c266ccd0364604e71 to < 840a1d3b77c1b062bd62b4733969a5b1efc274ceaffectedbe1eb7f78aa8fbe34779c56c266ccd0364604e71 to < a006aa3eedb8bfd6fe317c3cfe9c86ffe76b2385affectedbe1eb7f78aa8fbe34779c56c266ccd0364604e71 to < 69c67d451fc19d88e54f7d97e8e7c093e08357e1affectedbe1eb7f78aa8fbe34779c56c266ccd0364604e71 to < b5a772adf45a32c68bef28e60621f12617161556affected
Linux Linux
Default version status: affected
5.4affected0 to < 5.4unaffected5.4.235 to ≤ 5.4.*unaffected5.10.173 to ≤ 5.10.*unaffected5.15.99 to ≤ 5.15.*unaffected6.1.16 to ≤ 6.1.*unaffected6.2.3 to ≤ 6.2.*unaffected6.3 to ≤ *unaffected
References
- https://git.kernel.org/stable/c/c61e7d182ee3f3f5ecf18a2964e303d49c539b52 ↗
- https://git.kernel.org/stable/c/796e02cca30a67322161f0745e5ce994bbe75605 ↗
- https://git.kernel.org/stable/c/840a1d3b77c1b062bd62b4733969a5b1efc274ce ↗
- https://git.kernel.org/stable/c/a006aa3eedb8bfd6fe317c3cfe9c86ffe76b2385 ↗
- https://git.kernel.org/stable/c/69c67d451fc19d88e54f7d97e8e7c093e08357e1 ↗
- https://git.kernel.org/stable/c/b5a772adf45a32c68bef28e60621f12617161556 ↗