crypto: xts - Handle EBUSY correctly
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: xts - Handle EBUSY correctly
As it is xts only handles the special return value of EINPROGRESS, which means that in all other cases it will free data related to the request.
However, as the caller of xts 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 xts code can free request-related data when a caller specifies MAY_BACKLOG and a request returns EBUSY. A backlogged request can then trigger a use-after-free. The input does not specify whether exploitation requires local or network access, authentication, or user interaction.
Engineers running the Linux kernel should check their deployments; affected versions were not provided.