crypto: essiv - Handle EBUSY correctly
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ be1eb7f78aa8fbe34779c56c266ccd0364604e71 · < b5a772adf45a32c68bef28e60621f12617161556| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's crypto essiv code does not handle EBUSY correctly. When a caller specifies MAY_BACKLOG, a backlogged request can trigger a use-after-free. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Engineers running the Linux kernel should check their versions; affected versions are not specified.